← previous blocknext block →recent activity
Analyzing
Block #102,801,123
24 transactions · 23 stateful · 2026-09-07 16:28:38 UTC
Parallelism
58/100
Blocked
65%
Avg conflicts / tx
2.42
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,801,123 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w119w923w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x601b351a…ad04
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xd0ec60a1…d242
0x1b6862…e19c
16 touches
28 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x8ceef8eb…7670
0x40c49f…2af0
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
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
45 conflicts on slot 0x601b351af8…48ad04
Audit this contract →
← previous block·next block →recent activity