← previous blocknext block →recent activity
Analyzing
Block #86,687,060
11 transactions · 7 stateful · 2026-07-09 19:36:27 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,687,060 · 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
1w03w14w25w36w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xb448b3f9…fdb9
0x34b655…2a6f
6 touches
3 conflicts
0xb13b96bd…a3cb
0x34b655…2a6f
6 touches
3 conflicts
0x1af19f5c…aee2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf34dfba…1d80
0x34b655…2a6f
4 touches
1 conflict
0xcf34dfba…1d81
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity