← previous blocknext block →recent activity
Analyzing
Block #70,863,561
8 transactions · 8 stateful · 2026-04-27 12:24:16 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,863,561 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w2
- 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
0x058a2b23…9815
0x065c9d…c394
4 touches
1 conflict
0x20b568d8…4e2d
0x065c9d…c394
4 touches
1 conflict
0x365a3df5…3782
0x065c9d…c394
4 touches
1 conflict
0x45a849fb…35ed
0x065c9d…c394
4 touches
1 conflict
0x400e64b7…56cd
0x065c9d…c394
3 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
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