← previous blocknext block →recent activity
Analyzing
Block #84,522,728
22 transactions · 18 stateful · 2026-06-29 18:57:18 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,522,728 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w012w113w014w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78c30df4…c54d
0xa6afd3…d132
4 touches
1 conflict
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0xf412c531…d397
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x45eb39a1…b8d5
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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-WETH/USDC
1 conflict on slot 0x78c30df483…6ec54d
Audit this contract →
← previous block·next block →recent activity