← previous blocknext block →recent activity
Analyzing
Block #86,987,092
44 transactions · 40 stateful · 2026-07-11 05:01:21 UTC
Parallelism
61/100
Blocked
73%
Avg conflicts / tx
3.05
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,987,092 · 44 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w38w09w111w012w113w214w315w416w517w618w727w328w432w433w534w635w536w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xc7a15219…7745
0xa6afd3…d132
10 touches
10 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
10 touches
10 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
8 touches
6 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity