← previous blocknext block →recent activity
Analyzing
Block #101,020,116
33 transactions · 23 stateful · 2026-09-01 10:37:28 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,020,116 · 33 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
1w04w05w17w010w011w116w217w322w223w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b2110ec…f507
0xd32edf…ff58
9 touches
10 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x64b18423…c4d0
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x1b2110ec65…e4f507
Audit this contract →
← previous block·next block →recent activity