← previous blocknext block →recent activity
Analyzing
Block #100,104,201
21 transactions · 20 stateful · 2026-08-29 05:44:56 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,104,201 · 21 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
1w02w13w24w35w47w08w110w314w515w417w218w520w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85629ca4…f18d
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x083a8763…5a7c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
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
10 conflicts on slot 0x85629ca4d6…30f18d
Audit this contract →
← previous block·next block →recent activity