← previous blocknext block →recent activity
Analyzing
Block #102,054,358
22 transactions · 22 stateful · 2026-09-05 01:27:17 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,054,358 · 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
1w02w13w24w35w46w58w19w213w615w216w317w321w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dd44b1d…3f9b
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf2e7bb96…1a56
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0x6dd44b1dcb…8c3f9b
Audit this contract →
← previous block·next block →recent activity