← previous blocknext block →recent activity
Analyzing
Block #86,220,241
11 transactions · 10 stateful · 2026-07-07 15:34:50 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,220,241 · 11 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
2w03w15w06w18w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e1faa73…bfbf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x4d4e1c79…d38e
0x34b655…2a6f
4 touches
1 conflict
0xa0002c18…c480
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
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 0x7e1faa73db…84bfbf
Audit this contract →
← previous block·next block →recent activity