← previous blocknext block →recent activity
Analyzing
Block #100,861,994
14 transactions · 13 stateful · 2026-08-31 21:22:01 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,861,994 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w29w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0xe2263bea…6aa2
0x34ae4d…3fc5
4 touches
1 conflict
0xeba56708…8cd7
0x34ae4d…3fc5
4 touches
1 conflict
0xf1a14809…56fd
0x34ae4d…3fc5
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: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity