← previous blocknext block →recent activity
Analyzing
Block #86,697,941
43 transactions · 37 stateful · 2026-07-09 20:49:00 UTC
Parallelism
58/100
Blocked
62%
Avg conflicts / tx
1.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,697,941 · 43 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w110w111w012w113w114w215w316w417w518w619w721w226w334w435w1142w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
8 touches
6 conflicts
0x017975b8…fd4c
0x34b655…2a6f
8 touches
6 conflicts
0x120933a6…dbe3
0x34b655…2a6f
8 touches
6 conflicts
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0xa9988419…9f45
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity