← previous blocknext block →recent activity
Analyzing
Block #100,626,859
25 transactions · 20 stateful · 2026-08-31 01:38:48 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,626,859 · 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
1w02w14w27w39w211w012w013w114w015w420w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5c1ef5…aec1
0xd32edf…ff58
9 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x6d5c5d72…914b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
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 0xef5c1ef5bd…94aec1
Audit this contract →
← previous block·next block →recent activity