← previous blocknext block →recent activity
Analyzing
Block #102,103,782
20 transactions · 18 stateful · 2026-09-05 05:38:01 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,103,782 · 20 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
1w02w13w24w35w46w47w58w011w012w115w116w217w118w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x917fd32d…e9a2
0xd32edf…ff58
9 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
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 0x917fd32d34…dae9a2
Audit this contract →
← previous block·next block →recent activity