← previous blocknext block →recent activity
Analyzing
Block #100,706,147
20 transactions · 20 stateful · 2026-08-31 08:17:38 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,706,147 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w18w49w310w513w414w015w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3740a0aa…0fc5
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
10 touches
10 conflicts
0xd0ec60a1…d241
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
15 conflicts on slot 0x3740a0aac0…410fc5
Audit this contract →
← previous block·next block →recent activity