← previous blocknext block →recent activity
Analyzing
Block #70,955,743
12 transactions · 10 stateful · 2026-04-27 22:38:01 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,955,743 · 12 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
2w04w1
- 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
0x1807d4fa…3a4d
0x065c9d…c394
4 touches
1 conflict
0x45e1f3e8…783d
0x065c9d…c394
4 touches
1 conflict
0x2d487a0a…89b8
0x065c9d…c394
3 touches
1 conflict
0x7abbc623…a71e
0x065c9d…c394
3 touches
1 conflict
0x6b8a2a8f…645a
0x065c9d…c394
2 touches
1 conflict
0x6a9cbbea…a6bd
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