← previous blocknext block →recent activity
Analyzing
Block #102,211,171
18 transactions · 17 stateful · 2026-09-05 14:42:19 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,211,171 · 18 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
1w02w13w24w35w46w57w411w012w013w114w515w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72461168…cea2
0xd32edf…ff58
11 touches
15 conflicts
0xb0e4f69d…34e8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
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
15 conflicts on slot 0x7246116864…24cea2
Audit this contract →
← previous block·next block →recent activity