← previous blocknext block →recent activity
Analyzing
Block #86,699,871
39 transactions · 34 stateful · 2026-07-09 21:01:53 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
2.21
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,699,871 · 39 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w18w29w010w111w012w113w114w215w316w417w518w619w720w821w923w125w226w1134w735w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x5d537073…cf27
0x34b655…2a6f
8 touches
6 conflicts
0x818e1296…f4d7
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity