← previous blocknext block →recent activity
Analyzing
Block #86,220,416
21 transactions · 20 stateful · 2026-07-07 15:36:00 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,220,416 · 21 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
2w03w04w15w210w111w012w113w214w315w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e1faa73…bfbf
0x34b655…2a6f
8 touches
6 conflicts
0x456f4453…91f0
0x34b655…2a6f
6 touches
3 conflicts
0x45ccae3f…6aff
0x34b655…2a6f
6 touches
3 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
6 touches
3 conflicts
0x81a9b9e0…2b7e
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7e1faa73db…84bfbf
Audit this contract →
← previous block·next block →recent activity