← previous blocknext block →recent activity
Analyzing
Block #92,060,890
22 transactions · 19 stateful · 2026-08-01 00:37:10 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,060,890 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w713w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e6d779f…9be7
0xd32edf…ff58
15 touches
28 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
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
28 conflicts on slot 0x5e6d779f46…9d9be7
Audit this contract →
← previous block·next block →recent activity