← previous blocknext block →recent activity
Analyzing
Block #71,089,696
25 transactions · 18 stateful · 2026-04-28 13:30:10 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,089,696 · 25 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
1w05w18w09w110w212w013w014w115w016w117w218w219w320w423w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0x4ab14837…e1b2
0x2a68ba…90c5
6 touches
3 conflicts
0x4381471a…9ac1
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x41755291…977f
0x131a2e…0da9
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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/AUSD
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity