← previous blocknext block →recent activity
Analyzing
Block #71,043,206
15 transactions · 14 stateful · 2026-04-28 08:20:28 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,043,206 · 15 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
1w02w15w07w18w19w210w311w412w513w614w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0xffe431af…8faa
0x131a2e…0da9
6 touches
3 conflicts
0x3d63a10e…72b4
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
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
15 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity