← previous blocknext block →recent activity
Analyzing
Block #84,575,562
20 transactions · 16 stateful · 2026-06-30 00:50:04 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,575,562 · 20 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
1w03w06w111w013w114w215w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x29686688…0598
0xa6afd3…d132
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
4 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
4 touches
1 conflict
0x0c969dde…6b06
0xa6afd3…d132
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity