← previous blocknext block →recent activity
Analyzing
Block #86,958,253
63 transactions · 44 stateful · 2026-07-11 01:48:39 UTC
Parallelism
71/100
Blocked
77%
Avg conflicts / tx
2.3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,958,253 · 63 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
1w02w13w24w35w49w012w115w216w218w420w528w029w130w231w332w436w537w647w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x1941b441…5889
0x34b655…2a6f
12 touches
15 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
10 touches
10 conflicts
0x77456d18…854c
0xd32edf…ff58
9 touches
10 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity