← previous blocknext block →recent activity
Analyzing
Block #100,249,072
18 transactions · 16 stateful · 2026-08-29 17:55:05 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,249,072 · 18 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
1w02w13w24w35w011w012w013w414w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b1465d5…b77e
0xd32edf…ff58
9 touches
10 conflicts
0x1bc60d21…087f
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…343f
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
10 conflicts on slot 0x6b1465d5b3…dfb77e
Audit this contract →
← previous block·next block →recent activity