← previous blocknext block →recent activity
Analyzing
Block #100,584,404
25 transactions · 22 stateful · 2026-08-30 22:05:14 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,584,404 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w013w214w315w316w317w422w023w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40afcb37…764e
0x34b655…2a6f
8 touches
6 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0x7e9d5d59…af64
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
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
6 conflicts on slot 0x40afcb378f…37764e
Audit this contract →
← previous block·next block →recent activity