← previous blocknext block →recent activity
Analyzing
Block #100,849,605
25 transactions · 21 stateful · 2026-08-31 20:19:42 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
1.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,849,605 · 25 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
1w02w13w24w35w36w47w58w613w714w416w519w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac4c0be1…ffec
0xd32edf…ff58
15 touches
28 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 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
0x10c19272…7442
0x1b6862…e19c
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
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
28 conflicts on slot 0xac4c0be10f…52ffec
Audit this contract →
← previous block·next block →recent activity