← previous blocknext block →recent activity
Analyzing
Block #93,749,129
25 transactions · 20 stateful · 2026-08-06 22:09:59 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,749,129 · 25 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
2w03w14w25w38w09w110w211w312w414w017w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16e954d9…ff32
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x91855e…ac7e
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x794b8f81…3eac
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
10 conflicts on slot 0x16e954d961…83ff32
Audit this contract →
← previous block·next block →recent activity