pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,911,206
← previous block
next block →
recent activity
Analyzing
Block #70,911,206
11 transactions · 9 stateful · 2026-04-27 17:41:32 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,206
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
updatePrices
#3
0x0c7abd22
· blocks 2
#4
0x98717539
#5
updateDataFeedsValuesPartial
#7
0x6463ffd1
· blocks 1
#9
0x39435dac
#10
setData
#6
0x0c7abd22
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w0
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66dd7dd6…adbc
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xef29e1f3…3b27
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:
0xd32edf66…9fff58
3 conflicts on slot
0x66dd7dd699…01adbc
Audit this contract →
← previous block
·
next block →
recent activity