pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,996,903
← previous block
next block →
recent activity
Analyzing
Block #70,996,903
13 transactions · 9 stateful · 2026-04-28 03:12:18 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,903
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f02609
#2
0x69f02609
#3
updatePrices
#4
updatePrices
#5
0x69f02609
#6
0xa96df62f
#7
0x69f02609
#8
0x98717539
· blocks 1
#10
updateDataFeedsValuesPartial
#11
0x6463ffd1
#12
setData
#9
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0e96c56b…6ac2
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x30a225d6…6679
0x34b655…2a6f
2 touches
0 conflicts
0x58ea0867…e009
0x34b655…2a6f
2 touches
0 conflicts
0x6119e238…6886
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity