← previous blocknext block →recent activity
Analyzing
Block #70,994,739
11 transactions · 9 stateful · 2026-04-28 02:57:54 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,994,739 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x62d3c911…5abd
0x065c9d…c394
6 touches
3 conflicts
0x0614abfc…5c45
0x065c9d…c394
3 touches
1 conflict
0x28c4bcb5…38dc
0x065c9d…c394
3 touches
1 conflict
0x29205409…0805
0x065c9d…c394
2 touches
1 conflict
0x29205409…0806
0x065c9d…c394
2 touches
1 conflict
0x0cb137a7…6a76
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 Vault (KURU-VAULT)
3 conflicts on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity