← previous blocknext block →recent activity
Analyzing
Block #102,211,381
30 transactions · 22 stateful · 2026-09-05 14:43:24 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,211,381 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w310w413w514w524w628w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf87b5e63…39e0
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x21d8e673…0680
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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
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
28 conflicts on slot 0xf87b5e63af…4f39e0
Audit this contract →
← previous block·next block →recent activity