← previous blocknext block →recent activity
Analyzing
Block #70,908,141
8 transactions · 6 stateful · 2026-04-27 17:21:08 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,908,141 · 8 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x1e822f74…9d9e
0x065c9d…c394
4 touches
1 conflict
0x115d2975…277b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7e828586…eddf
0x065c9d…c394
4 touches
1 conflict
0x833f8521…8cb8
0x065c9d…c394
4 touches
1 conflict
0x5e8831a1…24f0
0x065c9d…c394
2 touches
1 conflict
0x5e8831a1…24f1
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