pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,956,152
10 transactions · 10 stateful · 2026-04-27 22:40:45 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,956,152 · 10 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24de5cd5…9828
0x065c9d…c394
6 touches
3 conflicts
0x39f92eaf…1a20
0x065c9d…c394
6 touches
3 conflicts
0x9edb9c8e…4b7c
0x065c9d…c394
6 touches
3 conflicts
0xcebc205d…8fee
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0x47b2d2eb…8aa5
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
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: 0x065c9d28…a9c394
3 conflicts on slot 0x24de5cd59d…749828
Audit this contract →
← previous block·next block →recent activity