← previous blocknext block →recent activity
Analyzing
Block #99,192,549
29 transactions · 26 stateful · 2026-08-26 01:02:06 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,192,549 · 29 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
1w02w13w24w37w49w510w611w712w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cbde4ac…9e4c
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
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 0x0cbde4ac80…0b9e4c
Audit this contract →
← previous block·next block →recent activity