pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,917,962
← previous block
next block →
recent activity
Analyzing
Block #70,917,962
11 transactions · 8 stateful · 2026-04-27 18:26:34 UTC
Parallelism
64
/100
Blocked
38
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,962
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#5
0xcf7468f4
#6
0xcf7468f4
#7
updateDataFeedsValuesPartial
#8
setData
#9
updatePrices
#10
updatePrices
#2
0x0c7abd22
· blocks 2
#3
0x0c7abd22
· blocks 1
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd214c750…93e3
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
2 touches
0 conflicts
0x00000000…008b
0x094452…0a09
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
6 conflicts on slot
0xd214c7504a…6e93e3
Audit this contract →
← previous block
·
next block →
recent activity