← previous blocknext block →recent activity
Analyzing
Block #70,891,533
18 transactions · 13 stateful · 2026-04-27 15:30:30 UTC
Parallelism
89/100
Blocked
23%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,891,533 · 18 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
6w07w18w112w013w1
- 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
0xa111ca58…52ce
0x065c9d…c394
4 touches
1 conflict
0x011fb8e3…054a
0x34b655…2a6f
4 touches
1 conflict
0x13739b9a…568d
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x3567d578…c3d6
0x34b655…2a6f
4 touches
1 conflict
0x3a6c42e0…fc44
0x34b655…2a6f
4 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