← previous blocknext block →recent activity
Analyzing
Block #86,612,083
21 transactions · 17 stateful · 2026-07-09 11:14:28 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,612,083 · 21 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
1w02w13w26w07w28w112w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7eed6327…b7ab
0x34b655…2a6f
4 touches
1 conflict
0xd0fb72b9…2d6d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfa667abe…bdfc
0x34b655…2a6f
4 touches
1 conflict
0x134b2009…e129
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x2e134f49…7fd9
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: Perpl
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity