← previous blocknext block →recent activity
Analyzing
Block #95,710,476
34 transactions · 30 stateful · 2026-08-13 19:07:51 UTC
Parallelism
74/100
Blocked
70%
Avg conflicts / tx
1.91
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #95,710,476 · 34 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
1w02w13w24w35w46w18w510w612w613w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x996ed6f4…e214
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c4
0x1b6862…e19c
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
36 conflicts on slot 0x996ed6f46f…b4e214
Audit this contract →
← previous block·next block →recent activity