← previous blocknext block →recent activity
Analyzing
Block #84,359,002
15 transactions · 14 stateful · 2026-06-29 00:45:40 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,359,002 · 15 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
1w05w06w17w09w010w111w112w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x975680c7…0e39
0xa6afd3…d132
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x7534f53d…6ed4
0x34b655…2a6f
4 touches
1 conflict
0xcfbcb055…7c86
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe0f1ea2a…a95d
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
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 0x975680c7cb…460e39
Audit this contract →
← previous block·next block →recent activity