← previous blocknext block →recent activity
Analyzing
Block #70,877,481
6 transactions · 5 stateful · 2026-04-27 13:57:00 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,877,481 · 6 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
0xb8b2d070…c50f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x004390c5…3059
0x065c9d…c394
4 touches
1 conflict
0x0f534bde…19c6
0x065c9d…c394
4 touches
1 conflict
0x3cc0b014…4e47
0x065c9d…c394
3 touches
1 conflict
0xb7b4c811…768b
0x065c9d…c394
2 touches
1 conflict
0xdb134e03…a2d1
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