pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#70,981,348
← previous block
next block →
recent activity
Analyzing
Block #70,981,348
9 transactions · 7 stateful · 2026-04-28 01:28:42 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,981,348
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
updatePrices
#7
updatePrices
#8
0x5d2fd812
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0001
0x158106…0e58
2 touches
0 conflicts
0x00000000…0006
0x158106…0e58
2 touches
0 conflicts
0x180c0e3b…5e1a
0x158106…0e58
2 touches
0 conflicts
0x3c26c817…24a6
0x158106…0e58
2 touches
0 conflicts
0x3e866b2d…214d
0x158106…0e58
2 touches
0 conflicts
0x89961a6e…201a
0x158106…0e58
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity