← previous blocknext block →recent activity
Analyzing
Block #100,605,649
48 transactions · 30 stateful · 2026-08-30 23:52:06 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
1.19
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,605,649 · 48 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
1w02w13w24w35w46w57w610w127w734w844w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x538ee5d9…7ff2
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…001f
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002f
0x1b6862…e19c
16 touches
28 conflicts
0xd25997d0…a68a
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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
36 conflicts on slot 0x538ee5d98e…f87ff2
Audit this contract →
← previous block·next block →recent activity