pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,908,899
← previous block
next block →
recent activity
Analyzing
Block #70,908,899
11 transactions · 10 stateful · 2026-04-27 17:26:10 UTC
Parallelism
64
/100
Blocked
40
%
Avg conflicts / tx
0.73
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,899
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 1
#3
forward
#4
0xed82b078
· blocks 3
#5
0xed82b078
· blocks 1
#7
updateDataFeedsValuesPartial
#10
setData
#2
updatePrices
#6
0xed82b078
· blocks 2
#8
0xed82b078
· blocks 1
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w0
6
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
4 touches
1 conflict
0x24968e6d…0132
0x131a2e…0da9
4 touches
1 conflict
0x00000000…000b
0x5075ea…d70f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xbbee74c2…567a
0x131a2e…0da9
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:
0x2a68ba18…8e90c5
6 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity