← previous blocknext block →recent activity
Analyzing
Block #100,083,565
25 transactions · 19 stateful · 2026-08-29 04:01:02 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,083,565 · 25 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
1w02w13w27w017w318w423w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x914043bb…bfc9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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
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 0x914043bb8a…c1bfc9
Audit this contract →
← previous block·next block →recent activity