← previous blocknext block →recent activity
Analyzing
Block #86,666,835
23 transactions · 22 stateful · 2026-07-09 17:21:25 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
1.91
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,666,835 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1951ee47…540f
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x3d4584df…ffed
0x34b655…2a6f
14 touches
21 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x288bc578…318e
0x34b655…2a6f
14 touches
21 conflicts
0x9ad66bbf…929c
0x34b655…2a6f
14 touches
21 conflicts
0xedcf2991…8551
0x34b655…2a6f
14 touches
21 conflicts
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
28 conflicts on slot 0x1951ee4781…b3540f
Audit this contract →
← previous block·next block →recent activity