← previous blocknext block →recent activity
Analyzing
Block #101,308,808
28 transactions · 21 stateful · 2026-09-02 10:50:11 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,308,808 · 28 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
1w07w18w210w011w312w413w014w118w320w421w123w124w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bfa67cf…18ee
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x6d43ee99…bdd8
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
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 0x6bfa67cf2a…6018ee
Audit this contract →
← previous block·next block →recent activity