← previous blocknext block →recent activity
Analyzing
Block #70,910,711
16 transactions · 15 stateful · 2026-04-27 17:38:14 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #70,910,711 · 16 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
3w06w07w08w19w010w111w212w313w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab14837…e1b2
0x2a68ba…90c5
8 touches
6 conflicts
0xbbee74c2…567a
0x131a2e…0da9
6 touches
4 conflicts
0x00000000…003d
0x131a2e…0da9
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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: MarginAccount
6 conflicts on slot 0x4ab14837eb…ffe1b2
Audit this contract →
← previous block·next block →recent activity