← previous blocknext block →recent activity
Analyzing
Block #95,297,158
19 transactions · 14 stateful · 2026-08-12 08:23:43 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,297,158 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w48w510w011w612w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b779b20…4fb6
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
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 0x3b779b2008…1f4fb6
Audit this contract →
← previous block·next block →recent activity