← previous blocknext block →recent activity
Analyzing
Block #86,844,682
12 transactions · 9 stateful · 2026-07-10 13:09:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,844,682 · 12 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
4w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc969f27…a960
0x34b655…2a6f
4 touches
1 conflict
0x0b277fb8…2d81
0x34b655…2a6f
4 touches
1 conflict
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x3e6563f1…1c23
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x52c6c14f…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x5a65207b…4f30
0x34b655…2a6f
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
1 conflict on slot 0xfc969f2707…d5a960
Audit this contract →
← previous block·next block →recent activity