← previous blocknext block →recent activity
Analyzing
Block #98,605,428
62 transactions · 58 stateful · 2026-08-23 23:25:05 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.95
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,605,428 · 62 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w18w210w013w014w115w218w019w120w031w233w435w336w137w238w339w549w450w551w656w258w1059w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x549dc324…3dd2
0x34b655…2a6f
10 touches
10 conflicts
0x261cbea7…e35d
0x34b655…2a6f
8 touches
6 conflicts
0x261cbea7…e35e
0x34b655…2a6f
8 touches
6 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 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
55 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity