← previous blocknext block →recent activity
Analyzing
Block #98,491,510
57 transactions · 42 stateful · 2026-08-23 13:32:11 UTC
Parallelism
60/100
Blocked
79%
Avg conflicts / tx
4.51
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,491,510 · 57 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
1w02w13w24w35w422w526w427w528w629w132w241w844w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
40 touches
190 conflicts
0x326a02b5…8dad
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
14 touches
21 conflicts
0x62910921…3016
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x6e682e01…c533
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
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
190 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity