← previous blocknext block →recent activity
Analyzing
Block #100,705,693
26 transactions · 19 stateful · 2026-08-31 08:15:20 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,705,693 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w39w410w511w613w014w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x5f77d607…2c84
0x065c9d…c394
12 touches
15 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
10 touches
10 conflicts
0x1b60b708…5b4b
0x34ae4d…3fc5
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
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-MON/USDC
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity