← previous blocknext block →recent activity
Analyzing
Block #99,878,446
22 transactions · 21 stateful · 2026-08-28 10:47:53 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,878,446 · 22 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
1w02w03w14w25w313w015w416w017w518w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c53666a…a1cb
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
10 conflicts on slot 0x0c53666a23…c8a1cb
Audit this contract →
← previous block·next block →recent activity