← previous blocknext block →recent activity
Analyzing
Block #86,220,646
20 transactions · 15 stateful · 2026-07-07 15:37:33 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,220,646 · 20 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
1w05w06w111w112w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
8 touches
6 conflicts
0x7c02c930…93ac
0x34b655…2a6f
6 touches
3 conflicts
0x181498e7…cd53
0x34b655…2a6f
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0xdc0c9700…ae04
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity