← previous blocknext block →recent activity
Analyzing
Block #94,967,501
16 transactions · 13 stateful · 2026-08-11 04:35:31 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,967,501 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w39w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x858fc671…e209
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x929f2b6c…f119
0x968279…9342
4 touches
1 conflict
0x929f2b6c…f11a
0x968279…9342
4 touches
1 conflict
0x929f2b6c…f11c
0x968279…9342
4 touches
1 conflict
0xd1bc79ff…989e
0x968279…9342
4 touches
1 conflict
0xd1bc79ff…989f
0x968279…9342
4 touches
1 conflict
0xd1bc79ff…98a2
0x968279…9342
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 0x858fc67129…20e209
Audit this contract →
← previous block·next block →recent activity