← previous blocknext block →recent activity
Analyzing
Block #71,066,178
9 transactions · 8 stateful · 2026-04-28 10:53:23 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,066,178 · 9 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x080674a3…e550
0x065c9d…c394
4 touches
1 conflict
0x9b6962e4…7e41
0x065c9d…c394
4 touches
1 conflict
0xe54ee200…960e
0x065c9d…c394
4 touches
1 conflict
0xf9730cd8…e76b
0x065c9d…c394
4 touches
1 conflict
0x0a85a226…83ba
0x1b6862…e19c
2 touches
0 conflicts
0xa1becda9…a5c9
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