← previous blocknext block →recent activity
Analyzing
Block #70,892,711
10 transactions · 8 stateful · 2026-04-27 15:38:21 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,892,711 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5cd1a50…84ed
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2ccae850…fdf3
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x55042839…fc22
0x065c9d…c394
4 touches
1 conflict
0xab15046e…7e6a
0x065c9d…c394
4 touches
1 conflict
0x3d0cbe61…421f
0x065c9d…c394
2 touches
1 conflict
0xcc8eb8ca…9312
0x065c9d…c394
2 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
1 conflict on slot 0xe5cd1a509e…bd84ed
Audit this contract →
← previous block·next block →recent activity