← previous blocknext block →recent activity
Analyzing
Block #102,107,096
22 transactions · 16 stateful · 2026-09-05 05:54:49 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,107,096 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w013w314w416w517w018w119w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fae453…17ec
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0baca3f8…1b65
0x065c9d…c394
4 touches
1 conflict
0xe783dfa4…5498
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
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
21 conflicts on slot 0xe6fae45369…3317ec
Audit this contract →
← previous block·next block →recent activity