← previous blocknext block →recent activity
Analyzing
Block #72,224,259
9 transactions · 7 stateful · 2026-05-03 19:32:09 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,224,259 · 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0624466c…833e
0x065c9d…c394
4 touches
1 conflict
0x1ca7e5d9…3b12
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x051ceff1…6799
0x065c9d…c394
3 touches
1 conflict
0xd83b0eda…3bbd
0x065c9d…c394
3 touches
1 conflict
0xfed4bbb3…f28d
0x065c9d…c394
3 touches
1 conflict
0xc88ad484…07bc
0x065c9d…c394
2 touches
0 conflicts
0xd663c0df…9364
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
1 conflict on slot 0x0624466c42…83833e
Audit this contract →
← previous block·next block →recent activity