← previous blocknext block →recent activity
Analyzing
Block #102,279,112
28 transactions · 24 stateful · 2026-09-05 20:26:36 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,279,112 · 28 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
1w02w13w24w06w07w18w29w311w112w217w118w223w024w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60b5ca0b…48b2
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x60b5ca0b6c…4f48b2
Audit this contract →
← previous block·next block →recent activity