← previous blocknext block →recent activity
Analyzing
Block #70,952,145
11 transactions · 10 stateful · 2026-04-27 22:14:05 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,952,145 · 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
5w06w17w2
- 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
0x1a64fc11…76d7
0x065c9d…c394
6 touches
3 conflicts
0x75f2f0cd…a6df
0x065c9d…c394
6 touches
3 conflicts
0xcff07ed5…9285
0x065c9d…c394
6 touches
3 conflicts
0xfa237f38…0b5f
0x065c9d…c394
6 touches
3 conflicts
0x215fb0dd…f04c
0x065c9d…c394
2 touches
1 conflict
0x2c80320f…d328
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