← previous blocknext block →recent activity
Analyzing
Block #86,357,436
9 transactions · 8 stateful · 2026-07-08 06:50:57 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,357,436 · 9 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
2w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5e57aea…6ff8
0x34b655…2a6f
4 touches
1 conflict
0xcc58c80b…ff79
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x0bf584e8…9ce5
0x34b655…2a6f
2 touches
0 conflicts
0x0e15356b…ef5b
0x34b655…2a6f
2 touches
0 conflicts
0x24efee95…58e4
0x34b655…2a6f
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 0xc5e57aeaa6…d36ff8
Audit this contract →
← previous block·next block →recent activity