← previous blocknext block →recent activity
Analyzing
Block #86,836,339
88 transactions · 65 stateful · 2026-07-10 12:13:45 UTC
Parallelism
74/100
Blocked
75%
Avg conflicts / tx
3.07
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #86,836,339 · 88 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w426w528w630w734w976w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…00c9
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x622b7f51…ea68
0xd32edf…ff58
17 touches
36 conflicts
0xea9e7e38…819b
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
12 touches
15 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity