← previous blocknext block →recent activity
Analyzing
Block #98,646,216
70 transactions · 52 stateful · 2026-08-24 02:57:10 UTC
Parallelism
64/100
Blocked
75%
Avg conflicts / tx
3.73
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #98,646,216 · 70 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
1w03w14w25w36w47w58w69w710w811w927w1028w429w532w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x4e38b373…0304
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001f
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002f
0x1b6862…e19c
20 touches
45 conflicts
0xd59f6ed1…03eb
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity