← previous blocknext block →recent activity
Analyzing
Block #100,121,213
22 transactions · 20 stateful · 2026-08-29 07:10:37 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,121,213 · 22 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
1w02w13w24w37w08w19w313w415w516w417w518w519w221w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae579152…fe51
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xed863ec8…90db
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0xae57915206…3efe51
Audit this contract →
← previous block·next block →recent activity