pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,863,637
← previous block
next block →
recent activity
Analyzing
Block #70,863,637
9 transactions · 7 stateful · 2026-04-27 12:24:46 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,863,637
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6463ffd1
#3
0x96e62922
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x69ef5606
#7
setData
#8
0x39435dac
#4
0x96e62922
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ebf69ec…edd2
0xd45826…f134
4 touches
1 conflict
0x00000000…00fc
0xd45826…f134
4 touches
1 conflict
0x00000000…0161
0xd45826…f134
4 touches
1 conflict
0x8ebf69ec…edcd
0xd45826…f134
4 touches
1 conflict
0xa8286f40…1016
0x065c9d…c394
2 touches
0 conflicts
0xbd47d7d4…3417
0x065c9d…c394
2 touches
0 conflicts
0xcc8305ba…86bc
0x065c9d…c394
2 touches
0 conflicts
0xd5b8f9b3…9e84
0x065c9d…c394
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
1 conflict on slot
0x8ebf69ec1d…1bedd2
Audit this contract →
← previous block
·
next block →
recent activity