pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,891,657
25 transactions · 17 stateful · 2026-04-27 15:31:20 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #70,891,657 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w515w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb746dd77…447c
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x2a1142af…c54d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x485d2778…aa5e
0x1b6862…e19c
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: 0xd32edf66…9fff58
15 conflicts on slot 0xb746dd77ce…0f447c
Audit this contract →
← previous block·next block →recent activity