← previous blocknext block →recent activity
Analyzing
Block #86,956,810
13 transactions · 10 stateful · 2026-07-11 01:39:01 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,956,810 · 13 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
3w05w17w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6a7552…a4b9
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x6c7e1952…d9c9
0x34b655…2a6f
4 touches
1 conflict
0x7ad73012…00e2
0x34b655…2a6f
4 touches
1 conflict
0x8dbcd0c9…9c1f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9debbac4…9a2a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0x5b6a755253…30a4b9
Audit this contract →
← previous block·next block →recent activity