← previous blocknext block →recent activity
Analyzing
Block #70,845,542
14 transactions · 12 stateful · 2026-04-27 10:24:15 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,845,542 · 14 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
4w05w110w012w1
- 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
0x3035b947…1a1d
0x065c9d…c394
4 touches
1 conflict
0x72c6181b…2653
0x065c9d…c394
4 touches
1 conflict
0xa8d199cd…5024
0x065c9d…c394
4 touches
1 conflict
0xf5c805d3…90c1
0x065c9d…c394
4 touches
1 conflict
0xc3aacf13…6b3d
0x34b655…2a6f
4 touches
1 conflict
0x1120dc00…efb7
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