← previous blocknext block →recent activity
Analyzing
Block #98,502,946
80 transactions · 69 stateful · 2026-08-23 14:30:30 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
2.46
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #98,502,946 · 80 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w616w117w221w728w729w830w964w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x47bef045…ffec
0xd32edf…ff58
19 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xe6e2ab64…a8f9
0x34b655…2a6f
12 touches
15 conflicts
0x6dedaff6…161b
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity