← previous blocknext block →recent activity
Analyzing
Block #86,835,626
13 transactions · 11 stateful · 2026-07-10 12:09:00 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,835,626 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xa8be2a01…a538
0x34b655…2a6f
3 touches
1 conflict
0xacdb0b5e…3feb
0x34b655…2a6f
3 touches
1 conflict
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0x8a7af3fd…72a7
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x62bfa76b…d2a2
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity