pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,862,228
7 transactions · 6 stateful · 2026-04-27 12:15:23 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,862,228 · 7 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
1w04w16w2
- 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
0x091ffda9…4f38
0x065c9d…c394
4 touches
1 conflict
0x28620644…ec7f
0x065c9d…c394
4 touches
1 conflict
0x5a902f82…9081
0x065c9d…c394
4 touches
1 conflict
0xb3e5d117…3cd2
0x065c9d…c394
4 touches
1 conflict
0x17358130…bab0
0x065c9d…c394
3 touches
1 conflict
0x00000000…0004
0x094452…0a09
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: 0xd0f8a642…83badc
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity