← previous blocknext block →recent activity
Analyzing
Block #101,311,288
26 transactions · 21 stateful · 2026-09-02 11:02:40 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,311,288 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w211w312w013w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x94035918…5973
0x065c9d…c394
3 touches
1 conflict
0x94035918…5974
0x065c9d…c394
3 touches
1 conflict
0xb0e93cc2…96e7
0x065c9d…c394
3 touches
1 conflict
0xc247fbe7…e835
0xd32edf…ff58
3 touches
1 conflict
0x130a02c9…70c2
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9287
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity