← previous blocknext block →recent activity
Analyzing
Block #98,524,750
37 transactions · 32 stateful · 2026-08-23 16:24:25 UTC
Parallelism
76/100
Blocked
69%
Avg conflicts / tx
1.65
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,524,750 · 37 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w518w320w621w422w523w628w529w730w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
14 touches
21 conflicts
0x23c4727d…753b
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0002
0xbb3f3c…e046
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
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
21 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity