← previous blocknext block →recent activity
Analyzing
Block #100,567,202
14 transactions · 12 stateful · 2026-08-30 20:38:42 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,567,202 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w28w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb40334f…e0bc
0xa6afd3…d132
6 touches
3 conflicts
0xefc629e7…776d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x7144ad06…b3e0
0xa6afd3…d132
3 touches
1 conflict
0x8a2f9a36…fb4a
0x354d92…66fb
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
3 conflicts on slot 0xdb40334f69…4ae0bc
Audit this contract →
← previous block·next block →recent activity