← previous blocknext block →recent activity
Analyzing
Block #86,963,364
18 transactions · 17 stateful · 2026-07-11 02:22:51 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
1.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,963,364 · 18 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
1w02w13w04w15w27w08w19w210w311w412w513w615w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xae901867…8086
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf982b915…898b
0x34b655…2a6f
8 touches
6 conflicts
0xae901867…8085
0x34b655…2a6f
8 touches
6 conflicts
0x75aa78e1…2176
0x34b655…2a6f
6 touches
3 conflicts
0x76736068…b82d
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity