← previous blocknext block →recent activity
Analyzing
Block #86,620,251
24 transactions · 20 stateful · 2026-07-09 12:09:01 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,620,251 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w314w017w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6f34e02…276b
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x472dd61b…64fe
0x34b655…2a6f
8 touches
6 conflicts
0x5379f516…8bf2
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
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
6 conflicts on slot 0xf6f34e02f9…26276b
Audit this contract →
← previous block·next block →recent activity