pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,911,085
← previous block
next block →
recent activity
Analyzing
Block #70,911,085
9 transactions · 8 stateful · 2026-04-27 17:40:44 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,085
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
#2
0x6463ffd1
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x69efa013
#6
setData
#7
0x39435dac
· blocks 1
#3
0x6463ffd1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0xf9ec9203…b6a2
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x28f424d9…4435
0x065c9d…c394
4 touches
1 conflict
0x43d040f7…8730
0x065c9d…c394
4 touches
1 conflict
0x9f48be7e…0030
0x065c9d…c394
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity