← previous blocknext block →recent activity
Analyzing
Block #86,104,367
18 transactions · 15 stateful · 2026-07-07 02:41:10 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,104,367 · 18 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
1w02w16w07w18w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f463838…072b
0x34b655…2a6f
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
6 touches
3 conflicts
0xc3b509f9…a9de
0x34b655…2a6f
6 touches
3 conflicts
0xdc0c9700…ae04
0x34b655…2a6f
6 touches
3 conflicts
0xddd20e39…d524
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x5f4638380f…31072b
Audit this contract →
← previous block·next block →recent activity