← previous blocknext block →recent activity
Analyzing
Block #98,335,840
42 transactions · 37 stateful · 2026-08-23 00:28:40 UTC
Parallelism
62/100
Blocked
65%
Avg conflicts / tx
2.48
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,335,840 · 42 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w312w314w119w423w425w227w528w229w332w634w835w936w1037w1138w1239w1340w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0x0bd5c557…de1e
0x34b655…2a6f
10 touches
10 conflicts
0xf98db8ee…a56d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity