← previous blocknext block →recent activity
Analyzing
Block #72,288,607
8 transactions · 7 stateful · 2026-05-04 02:44:40 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,288,607 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8ca64ffc…f0c0
0x065c9d…c394
4 touches
1 conflict
0xefb03ae4…da55
0x065c9d…c394
4 touches
1 conflict
0x507af483…21f1
0x065c9d…c394
3 touches
1 conflict
0x26bca9dd…b64b
0x065c9d…c394
3 touches
1 conflict
0x338bf96e…b640
0x065c9d…c394
3 touches
1 conflict
0xf09eb56f…c1f8
0x065c9d…c394
2 touches
0 conflicts
0xf93a2b29…dd13
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity