← previous blocknext block →recent activity
Analyzing
Block #86,491,699
22 transactions · 19 stateful · 2026-07-08 21:48:23 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,491,699 · 22 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
2w03w14w05w06w17w18w210w311w014w016w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba422af…42ec
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x1067563b…3ed7
0x34b655…2a6f
6 touches
3 conflicts
0x4ae0d602…8c0d
0x34b655…2a6f
4 touches
1 conflict
0x68e52406…3352
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcf0714ef…913e
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
3 conflicts on slot 0xdba422aff7…3642ec
Audit this contract →
← previous block·next block →recent activity