← previous blocknext block →recent activity
Analyzing
Block #72,572,217
9 transactions · 9 stateful · 2026-05-05 10:14:05 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,572,217 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xbeb9fd23…b39e
0x065c9d…c394
3 touches
1 conflict
0xcdffc519…8250
0x065c9d…c394
3 touches
1 conflict
0xa36ce883…837d
0x065c9d…c394
3 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x1a4b4152…0a08
0x8d0464…4402
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
1 conflict on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity