← previous blocknext block →recent activity
Analyzing
Block #86,493,685
22 transactions · 18 stateful · 2026-07-08 22:01:39 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,493,685 · 22 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
1w02w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa2bfeb…ca33
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf79b64ad…1865
0xd32edf…ff58
3 touches
1 conflict
0xf047b0c5…2800
0x0080dd…0df2
2 touches
0 conflicts
0xf047b0c5…2802
0x0080dd…0df2
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 0x4aa2bfeb56…ccca33
Audit this contract →
← previous block·next block →recent activity