← previous blocknext block →recent activity
Analyzing
Block #100,028,940
24 transactions · 22 stateful · 2026-08-28 23:26:04 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,028,940 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w59w611w012w413w514w618w519w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86e11f16…c8bc
0xd32edf…ff58
9 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x86e11f16e8…71c8bc
Audit this contract →
← previous block·next block →recent activity