pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,956,644
← previous block
next block →
recent activity
Analyzing
Block #70,956,644
10 transactions · 8 stateful · 2026-04-27 22:44:02 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,644
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6463ffd1
· blocks 1
#2
forward
#3
updateDataFeedsValuesPartial
#5
setData
#6
0x55e58ed0
#7
0xb0435a94
#8
0x69efe729
#9
updatePrices
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa61643a1…3a42
0x065c9d…c394
3 touches
1 conflict
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…003d
0x065c9d…c394
2 touches
0 conflicts
0x223d0d71…76af
0x065c9d…c394
2 touches
0 conflicts
0x840e7caa…2db0
0x065c9d…c394
2 touches
0 conflicts
0xccd93d4e…1e8e
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:
0x065c9d28…a9c394
1 conflict on slot
0xa61643a1f8…463a42
Audit this contract →
← previous block
·
next block →
recent activity