pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,845,951
12 transactions · 11 stateful · 2026-04-27 10:26:57 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,845,951 · 12 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
5w06w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x31a80474…3130
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0xc85a87e9…b159
0x065c9d…c394
5 touches
3 conflicts
0xb7bc1a95…446c
0x065c9d…c394
5 touches
3 conflicts
0xf4446dcb…0b94
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity