← previous blocknext block →recent activity
Analyzing
Block #70,863,463
9 transactions · 8 stateful · 2026-04-27 12:23:37 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,863,463 · 9 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
4w06w1
- 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
0x2ded1fb1…2ad5
0x065c9d…c394
4 touches
1 conflict
0x5345ec7d…d823
0x065c9d…c394
3 touches
1 conflict
0x0095fd0d…0d28
0x065c9d…c394
2 touches
1 conflict
0x0e1700c8…1526
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