← previous blocknext block →recent activity
Analyzing
Block #103,050,023
22 transactions · 21 stateful · 2026-09-08 13:21:51 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,050,023 · 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
1w02w13w24w35w47w110w511w012w119w020w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2871366…34b4
0xd32edf…ff58
13 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x27824ec7…7816
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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 0xa287136678…b334b4
Audit this contract →
← previous block·next block →recent activity