← previous blocknext block →recent activity
Analyzing
Block #101,060,862
16 transactions · 10 stateful · 2026-09-01 14:02:28 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,060,862 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xea7ebe9d…709e
0x34ae4d…3fc5
4 touches
1 conflict
0x10d80fee…dbda
0x34ae4d…3fc5
4 touches
1 conflict
0x0b104f98…d9ee
0xc8689a…ee79
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb002781d…04af
0xa6afd3…d132
3 touches
1 conflict
0xe2263bea…6a9f
0x34ae4d…3fc5
2 touches
0 conflicts
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: Market-WETH/USDC
1 conflict on slot 0x42daad7f35…6b630b
Audit this contract →
← previous block·next block →recent activity