pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,381,362
13 transactions · 11 stateful · 2026-04-25 06:52:38 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,381,362 · 13 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
1w05w07w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x3a8662b0…dcdc
0x065c9d…c394
3 touches
1 conflict
0x8e388c1c…e3ea
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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 0xcf3283bab2…c3c9fa
Audit this contract →
← previous block·next block →recent activity