← previous blocknext block →recent activity
Analyzing
Block #93,879,848
35 transactions · 26 stateful · 2026-08-07 09:07:08 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #93,879,848 · 35 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
1w03w14w26w310w412w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12606f0e…1f16
0xd32edf…ff58
17 touches
36 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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
36 conflicts on slot 0x12606f0ef0…1b1f16
Audit this contract →
← previous block·next block →recent activity