← previous blocknext block →recent activity
Analyzing
Block #86,956,952
22 transactions · 20 stateful · 2026-07-11 01:39:58 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,956,952 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w210w311w412w514w115w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45c033be…0aad
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xb06917e8…6985
0x34b655…2a6f
6 touches
3 conflicts
0xa8492b67…775d
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
10 conflicts on slot 0x45c033beaa…a40aad
Audit this contract →
← previous block·next block →recent activity