← previous blocknext block →recent activity
Analyzing
Block #100,605,394
19 transactions · 15 stateful · 2026-08-30 23:50:49 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,605,394 · 19 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
1w02w13w24w35w46w58w59w613w614w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf78b7b1…3efe
0xd32edf…ff58
13 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x35801c67…bcc5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0xd539bd36…9401
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xaf78b7b1f5…e93efe
Audit this contract →
← previous block·next block →recent activity