← previous blocknext block →recent activity
Analyzing
Block #72,500,545
10 transactions · 10 stateful · 2026-05-05 02:16:53 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,500,545 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2b5ba73e…fb22
0x065c9d…c394
3 touches
1 conflict
0x3ea4fe32…7e7c
0x065c9d…c394
2 touches
0 conflicts
0x416f1911…b0aa
0x065c9d…c394
2 touches
0 conflicts
0x4f900fbe…7a81
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0xa7f7fe85…b0f3
0x065c9d…c394
2 touches
0 conflicts
0xdacef0f8…63c1
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity