← previous blocknext block →recent activity
Analyzing
Block #102,436,522
108 transactions · 88 stateful · 2026-09-06 09:44:02 UTC
Parallelism
96/100
Blocked
6%
Avg conflicts / tx
0.08
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,436,522 · 108 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
1w010w113w220w021w126w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250a444b…2f5a
0xd32edf…ff58
7 touches
6 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x250a444b16…062f5a
Audit this contract →
← previous block·next block →recent activity