← previous blocknext block →recent activity
Analyzing
Block #100,809,590
50 transactions · 37 stateful · 2026-08-31 16:58:12 UTC
Parallelism
80/100
Blocked
51%
Avg conflicts / tx
1.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,809,590 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w211w512w621w733w837w941w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f382f57…0ea9
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 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…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x91945265…e58e
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 0x2f382f5741…0f0ea9
Audit this contract →
← previous block·next block →recent activity