← previous blocknext block →recent activity
Analyzing
Block #101,322,523
25 transactions · 22 stateful · 2026-09-02 11:59:11 UTC
Parallelism
80/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,322,523 · 25 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
1w02w13w25w18w29w310w411w012w113w218w220w321w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xa919080c…b1c7
0x065c9d…c394
5 touches
3 conflicts
0xbc240a62…0e19
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x59658b83…222a
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: Kuru Exchange: MarginAccount
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity