← previous blocknext block →recent activity
Analyzing
Block #86,700,299
13 transactions · 11 stateful · 2026-07-09 21:04:45 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,700,299 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd75d6f7…dc18
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e3
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e4
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x2fcaf77d…8bec
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc1251c8d…2b25
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 0xdd75d6f728…fbdc18
Audit this contract →
← previous block·next block →recent activity