← previous blocknext block →recent activity
Analyzing
Block #99,626,225
75 transactions · 52 stateful · 2026-08-27 13:32:06 UTC
Parallelism
68/100
Blocked
79%
Avg conflicts / tx
2.99
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #99,626,225 · 75 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w511w612w713w826w940w1048w1553w1754w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf68d3544…bb24
0xd32edf…ff58
27 touches
91 conflicts
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
16 touches
28 conflicts
0x9ac040c1…8222
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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
91 conflicts on slot 0xf68d35443f…f0bb24
Audit this contract →
← previous block·next block →recent activity