← previous blocknext block →recent activity
Analyzing
Block #86,221,051
22 transactions · 21 stateful · 2026-07-07 15:40:13 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,221,051 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w18w19w010w111w113w214w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1526b11f…8b21
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb56f0740…7542
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd5a25205…645e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x109d8a52…a7b7
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 0x1526b11fec…5a8b21
Audit this contract →
← previous block·next block →recent activity