← previous blocknext block →recent activity

Analyzing

Block #70,955,776

5 transactions · 5 stateful · 2026-04-27 22:38:15 UTC

Parallelism

60/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,955,776  ·  5 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

- 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

0x3ce3d006…85fb

0x065c9d…c394

4 touches
1 conflict

0x3da11c10…aa48

0x065c9d…c394

4 touches
1 conflict

0xc46135b2…8002

0x065c9d…c394

4 touches
1 conflict

0xfbaa0f48…cb53

0x065c9d…c394

4 touches
1 conflict

0x11542808…561a

0x065c9d…c394

2 touches
1 conflict

0x9c6f0d2e…0c0f

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

← previous block·next block →recent activity