The number of times that the port was unable to transmit frames because the transmit BB credit was zero. The purpose of this statistic is to detect congestion or a device affected by latency. This parameter is sampled at intervals of 2.5 microseconds, and the counter is incremented if the condition is true. Each sample represents 2.5 microseconds of time with zero Tx BB Credit. An increment of this counter means that the frames could not be sent to the attached device for 2.5 microseconds, indicating degraded performance.

2.5 microseconds * 400 000 = one minute
if you hit the 400k mark your link is bottlenecked and has no possibility to transmit frames.

XorMon presents time in % when the port was unable to transmit frames.
100% means that the port has no possibility to send anything for the given time frame.
Switch and Total aggregated graphs make a summary of all per port % then the result can go above 100% what does not have to be wrong if you have many ports.

BBCredits % vs. IBM Port Congestion Index

IBM Storage Insights reports a similar metric called the Port Congestion Index (PCI) — a 0-100+ score built from the same buffer-credit-zero counter (tim_txcrd_z), but additionally scaled against the port's Send Bandwidth %, using a formula IBM does not publish.
The practical difference is that BBCredits % is a direct, transparent percentage of time the port was blocked on buffer credits, while IBM Storage Insights PCI is that same signal run through an undisclosed, bandwidth-dependent scaling — which IBM's own support documentation confirms can inflate the index on low-traffic ports, to the point where IBM recommends adding a minimum-bandwidth exclusion to alert policies to suppress false positives.
XorMon uses BBCredits % instead because it needs no such workaround: the formula is fully documented above, the result is directly comparable to Brocade/Broadcom's own guidance (~10% = attention, ~20%+ = real problem), and it's calculated the same way regardless of vendor or collection method (SNMP or REST API).