← previous blocknext block →recent activity
Analyzing
Block #100,875,541
64 transactions · 63 stateful · 2026-08-31 22:30:10 UTC
Parallelism
92/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,875,541 · 64 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
1w02w13w05w16w27w38w49w010w163w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efaeba3…547b
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
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 0x9efaeba3c4…6d547b
Audit this contract →
← previous block·next block →recent activity