pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,892,262
← previous block
next block →
recent activity
Analyzing
Block #70,892,262
12 transactions · 8 stateful · 2026-04-27 15:35:22 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,262
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updatePrices
#5
forward
#6
forward
#7
0xed82b078
#8
0xed82b078
#9
updateDataFeedsValuesPartial
#10
setData
#11
updatePrices
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…0000
0xc1a578…8e1a
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
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity