← previous blocknext block →recent activity
Analyzing
Block #86,708,044
28 transactions · 20 stateful · 2026-07-09 21:56:25 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.14
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,708,044 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0x9e7a5a50…42a8
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5ea
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5eb
0x34b655…2a6f
14 touches
21 conflicts
0x3151b440…d0aa
0x34b655…2a6f
14 touches
21 conflicts
0x5e0b8bbe…377b
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity