← previous blocknext block →recent activity
Analyzing
Block #86,047,724
14 transactions · 11 stateful · 2026-07-06 20:23:27 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,047,724 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xa5ff1356…a59d
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x4d7057a9…1c18
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity