← previous blocknext block →recent activity
Analyzing
Block #73,214,354
11 transactions · 9 stateful · 2026-05-08 09:30:45 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,214,354 · 11 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
1w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9758a71b…2438
0x065c9d…c394
4 touches
1 conflict
0x9d8d9bfb…dee0
0x065c9d…c394
4 touches
1 conflict
0x744cd91c…69fe
0x065c9d…c394
3 touches
1 conflict
0x78177a3f…5ce1
0x065c9d…c394
3 touches
1 conflict
0xcff79070…50e8
0x065c9d…c394
3 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
2 touches
0 conflicts
0xfec5772d…b77f
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