← previous blocknext block →recent activity
Analyzing
Block #86,232,452
13 transactions · 12 stateful · 2026-07-07 16:56:22 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,232,452 · 13 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
1w02w03w16w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0x6fe752ed…4d3b
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xec0e0220…cb90
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity