← previous blocknext block →recent activity
Analyzing
Block #100,727,907
30 transactions · 25 stateful · 2026-08-31 10:07:06 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,727,907 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w27w48w511w614w416w518w619w329w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bd5f58…3e0b
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdd4
0x1b6862…e19c
8 touches
6 conflicts
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 0xe5bd5f58ff…4f3e0b
Audit this contract →
← previous block·next block →recent activity