← previous blocknext block →recent activity
Analyzing
Block #70,863,670
7 transactions · 6 stateful · 2026-04-27 12:25:00 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,863,670 · 7 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
2w03w15w06w1
- 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
0x06c50c38…7a74
0x065c9d…c394
4 touches
1 conflict
0x091ffda9…4f38
0x065c9d…c394
4 touches
1 conflict
0xcacddecb…01df
0x065c9d…c394
4 touches
1 conflict
0xd5b8f9b3…9e84
0x065c9d…c394
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xd11dc26e…59ab
0x34b655…2a6f
4 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