← previous blocknext block →recent activity
Analyzing
Block #102,019,146
24 transactions · 19 stateful · 2026-09-04 22:28:57 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,019,146 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w215w316w017w122w023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd52ad835…2c5f
0xd32edf…ff58
7 touches
6 conflicts
0x6d43ee99…bdd6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xd52ad83538…5d2c5f
Audit this contract →
← previous block·next block →recent activity