← previous blocknext block →recent activity
Analyzing
Block #70,997,065
6 transactions · 5 stateful · 2026-04-28 03:13:22 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,997,065 · 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
1w02w1
- 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
0x2b42047a…c15c
0x065c9d…c394
4 touches
1 conflict
0x72d28f6f…b567
0x065c9d…c394
4 touches
1 conflict
0x801bc856…fa2b
0x065c9d…c394
4 touches
1 conflict
0xcc8da7d3…15fb
0x065c9d…c394
4 touches
1 conflict
0xeda03a4e…c106
0x065c9d…c394
4 touches
1 conflict
0x6d180319…1910
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