← previous blocknext block →recent activity
Analyzing
Block #86,915,354
20 transactions · 14 stateful · 2026-07-10 21:02:02 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,915,354 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w211w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb46ee126…a1a5
0x34b655…2a6f
6 touches
3 conflicts
0x342cf4de…0a48
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0xe727ab72…768b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x549f612f…0565
0x34b655…2a6f
6 touches
3 conflicts
0x5b89526e…c61c
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xb46ee12643…9ca1a5
Audit this contract →
← previous block·next block →recent activity