← previous blocknext block →recent activity
Analyzing
Block #98,264,966
55 transactions · 48 stateful · 2026-08-22 18:32:03 UTC
Parallelism
55/100
Blocked
73%
Avg conflicts / tx
4.44
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #98,264,966 · 55 txs across 25 waves · depth 25
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
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w520w621w730w631w732w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
40 touches
190 conflicts
0xb6c4b1a8…05fd
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0018
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0028
0x1b6862…e19c
14 touches
21 conflicts
0xd59f6ed1…03e4
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 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