pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,862,471
← previous block
next block →
recent activity
Analyzing
Block #70,862,471
14 transactions · 13 stateful · 2026-04-27 12:17:00 UTC
Parallelism
79
/100
Blocked
15
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,862,471
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
revealWithCallback
· blocks 2
#5
revealWithCallback
#6
revealWithCallback
#7
revealWithCallback
#8
updatePrices
#9
0x98717539
#10
updateDataFeedsValuesPartial
#11
setData
#12
0x6463ffd1
#13
0x69ef5434
#3
revealWithCallback
· blocks 1
#4
revealWithCallback
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ebf69ec…edd3
0xd45826…f134
6 touches
3 conflicts
0x8ebf69ec…edd4
0xd45826…f134
6 touches
3 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
0xd458261e…e6f134
3 conflicts on slot
0x8ebf69ec1d…1bedd3
Audit this contract →
← previous block
·
next block →
recent activity