← previous blocknext block →recent activity
Analyzing
Block #84,523,336
30 transactions · 24 stateful · 2026-06-29 19:01:20 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,523,336 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w214w015w116w217w318w324w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x78c30df4…c54d
0xa6afd3…d132
6 touches
3 conflicts
0x49b0842d…0a93
0x34b655…2a6f
6 touches
3 conflicts
0xf412c531…d397
0xa6afd3…d132
6 touches
3 conflicts
0x9ff2b017…3fa2
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 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-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity