← previous blocknext block →recent activity
Analyzing
Block #73,817,203
9 transactions · 8 stateful · 2026-05-11 04:38:04 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,817,203 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x427ae3dd…d10e
0x065c9d…c394
2 touches
0 conflicts
0x5eba0358…3b4d
0x065c9d…c394
2 touches
0 conflicts
0x600e3deb…5a87
0x065c9d…c394
2 touches
0 conflicts
0xc7faedd3…1e68
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity