pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,862,209
← previous block
next block →
recent activity
Analyzing
Block #70,862,209
8 transactions · 8 stateful · 2026-04-27 12:15:16 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,862,209
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xccf50a51
· blocks 2
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#2
0x42dd8743
· blocks 1
#3
0x6463ffd1
· blocks 1
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67152eb2…d12b
0x065c9d…c394
5 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x091ffda9…4f38
0x065c9d…c394
4 touches
1 conflict
0x27150329…d896
0x065c9d…c394
4 touches
1 conflict
0xb3e5d117…3cd2
0x065c9d…c394
4 touches
1 conflict
0xb7d5028a…a15e
0x065c9d…c394
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
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
3 conflicts on slot
0x67152eb2aa…23d12b
Audit this contract →
← previous block
·
next block →
recent activity