← previous blocknext block →recent activity
Analyzing
Block #86,904,214
25 transactions · 24 stateful · 2026-07-10 19:47:35 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,904,214 · 25 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
1w02w14w05w06w17w28w311w112w413w514w618w219w321w723w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7babfe9a…ff96
0x34b655…2a6f
10 touches
10 conflicts
0xc7a15219…7745
0xa6afd3…d132
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
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
10 conflicts on slot 0x7babfe9a22…93ff96
Audit this contract →
← previous block·next block →recent activity