← previous blocknext block →recent activity
Analyzing
Block #101,093,900
33 transactions · 27 stateful · 2026-09-01 16:49:01 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,093,900 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w110w619w720w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a59bb7…1bb3
0xd32edf…ff58
19 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
16 touches
28 conflicts
0x0a85a226…83ba
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0028
0x1b6862…e19c
16 touches
28 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
45 conflicts on slot 0xc9a59bb7dd…da1bb3
Audit this contract →
← previous block·next block →recent activity