← previous blocknext block →recent activity
Analyzing
Block #93,504,038
17 transactions · 13 stateful · 2026-08-06 01:37:53 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,504,038 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ba379f5…96f3
0xd32edf…ff58
11 touches
15 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x4c1a8dbe…e18f
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
2 touches
0 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
15 conflicts on slot 0x6ba379f5e9…0596f3
Audit this contract →
← previous block·next block →recent activity