← previous blocknext block →recent activity
Analyzing
Block #101,061,590
21 transactions · 18 stateful · 2026-09-01 14:06:08 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,061,590 · 21 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
1w02w13w24w311w012w013w314w115w418w519w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6befc03c…8e67
0xd32edf…ff58
7 touches
6 conflicts
0xb26ff3de…9352
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x6d43ee99…bdd3
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
6 conflicts on slot 0x6befc03c76…7e8e67
Audit this contract →
← previous block·next block →recent activity