← previous blocknext block →recent activity
Analyzing
Block #84,490,286
10 transactions · 9 stateful · 2026-06-29 15:20:50 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,490,286 · 10 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
1w03w04w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3287e4ec…eaa3
0xa6afd3…d132
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0058de6c…c895
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x44966858…1d1a
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
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 0x3287e4ecfd…5aeaa3
Audit this contract →
← previous block·next block →recent activity