← previous blocknext block →recent activity
Analyzing
Block #102,061,985
16 transactions · 13 stateful · 2026-09-05 02:05:56 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,061,985 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc930908…d5fe
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
2 touches
0 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
6 conflicts on slot 0xcc9309085d…f1d5fe
Audit this contract →
← previous block·next block →recent activity