← previous blocknext block →recent activity
Analyzing
Block #100,635,068
21 transactions · 17 stateful · 2026-08-31 02:20:06 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,635,068 · 21 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
1w06w17w28w39w410w512w013w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x68106229…7057
0xa6afd3…d132
8 touches
6 conflicts
0xeba56708…8cd7
0x34ae4d…3fc5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbdb88071…cdf1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
4 touches
1 conflict
0xa8c9c3f1…c4c5
0xa6afd3…d132
3 touches
2 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: MarginAccount
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity