← previous blocknext block →recent activity
Analyzing
Block #100,790,399
50 transactions · 37 stateful · 2026-08-31 15:21:38 UTC
Parallelism
78/100
Blocked
65%
Avg conflicts / tx
1.76
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,790,399 · 50 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w414w515w616w717w818w919w1022w145w247w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fcdffc4…26dc
0xd32edf…ff58
21 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a84d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
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
55 conflicts on slot 0x9fcdffc4c4…e526dc
Audit this contract →
← previous block·next block →recent activity