← previous blocknext block →recent activity
Analyzing
Block #86,315,369
26 transactions · 23 stateful · 2026-07-08 02:10:03 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,315,369 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w08w111w015w116w119w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
8 touches
6 conflicts
0x1bf2d56b…6c10
0xd32edf…ff58
7 touches
6 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x37cd7d01…88f0
0x34b655…2a6f
4 touches
1 conflict
0x39165d97…39c2
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity