← previous blocknext block →recent activity
Analyzing
Block #100,588,263
28 transactions · 27 stateful · 2026-08-30 22:24:39 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,588,263 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w07w48w510w211w314w315w416w517w519w620w721w824w927w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
8 touches
6 conflicts
0x38d6111f…33a0
0x34b655…2a6f
8 touches
6 conflicts
0x3ac0ecfd…fc73
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity