← previous blocknext block →recent activity
Analyzing
Block #86,609,441
22 transactions · 18 stateful · 2026-07-09 10:56:51 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,609,441 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w38w19w414w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0bc3bf8…e2b1
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x1e80597b…ec89
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x46fdaf87…2819
0x34b655…2a6f
8 touches
6 conflicts
0x5b7d1494…ed87
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x67eb9f2d…885a
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xb0bc3bf895…20e2b1
Audit this contract →
← previous block·next block →recent activity