← previous blocknext block →recent activity
Analyzing
Block #100,587,594
24 transactions · 21 stateful · 2026-08-30 22:21:16 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,587,594 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w010w411w512w613w414w115w016w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f9c6e40…0e64
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x792299c4…16b7
0x1b6862…e19c
6 touches
3 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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
21 conflicts on slot 0x6f9c6e40a9…c20e64
Audit this contract →
← previous block·next block →recent activity