← previous blocknext block →recent activity
Analyzing
Block #100,462,198
15 transactions · 14 stateful · 2026-08-30 11:50:27 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,462,198 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w47w510w311w613w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x7aa38190…a0c4
0x34b655…2a6f
10 touches
10 conflicts
0x1a2055c7…9054
0x34b655…2a6f
10 touches
10 conflicts
0x4bf59d22…00de
0x34b655…2a6f
10 touches
10 conflicts
0x640c4fb2…044a
0x34b655…2a6f
9 touches
10 conflicts
0xc2aacf41…5501
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity