← previous blocknext block →recent activity
Analyzing
Block #86,933,505
16 transactions · 14 stateful · 2026-07-10 23:03:20 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,933,505 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w18w210w311w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e10ffaa…5365
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x83bf1cc7…260e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
4 touches
1 conflict
0xe7723b6a…bd79
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 0x4e10ffaa64…365365
Audit this contract →
← previous block·next block →recent activity