← previous blocknext block →recent activity
Analyzing
Block #86,220,534
25 transactions · 18 stateful · 2026-07-07 15:36:48 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,220,534 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w111w012w114w215w216w019w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
6 touches
3 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
4 touches
1 conflict
0x655a3e2f…3aca
0x34b655…2a6f
4 touches
1 conflict
0x807e52bc…9905
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
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
6 conflicts on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity