← previous blocknext block →recent activity
Analyzing
Block #99,210,026
35 transactions · 29 stateful · 2026-08-26 02:30:01 UTC
Parallelism
74/100
Blocked
62%
Avg conflicts / tx
1.51
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,210,026 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w58w613w716w818w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01d63611…5203
0xd32edf…ff58
17 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0xd4c913d7…343b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 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
36 conflicts on slot 0x01d63611b5…b25203
Audit this contract →
← previous block·next block →recent activity