← previous blocknext block →recent activity
Analyzing
Block #70,845,591
9 transactions · 7 stateful · 2026-04-27 10:24:34 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,845,591 · 9 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x08fc3429…16d4
0x065c9d…c394
4 touches
1 conflict
0x4a27b231…434d
0x065c9d…c394
4 touches
1 conflict
0xdb0e25f0…f13e
0x065c9d…c394
4 touches
1 conflict
0xafb9463d…0bae
0x065c9d…c394
4 touches
1 conflict
0xc6c8794d…eccb
0x065c9d…c394
2 touches
1 conflict
0xdd5e5942…3a9e
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)
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity