← previous blocknext block →recent activity
Analyzing
Block #71,037,895
7 transactions · 6 stateful · 2026-04-28 07:45:06 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,037,895 · 7 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
4w05w1
- 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
0x51104ada…f25c
0x065c9d…c394
4 touches
1 conflict
0x77c42667…dbc4
0x065c9d…c394
4 touches
1 conflict
0x87ece408…e446
0x065c9d…c394
4 touches
1 conflict
0x03fdf70d…2ab2
0x065c9d…c394
3 touches
1 conflict
0x21677e05…6778
0x065c9d…c394
2 touches
1 conflict
0x21677e05…6777
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