pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,981,843
← previous block
next block →
recent activity
Analyzing
Block #70,981,843
12 transactions · 6 stateful · 2026-04-28 01:32:00 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,981,843
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe98321…befd
#2
0x69f00e88
#3
0x69f00e88
#4
updatePrices
· blocks 1
#6
updatePrices
#7
0x69f00e88
#8
0x69f00e88
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23f382f2…f742
0x34b655…2a6f
2 touches
0 conflicts
0x3a995fd9…b426
0x34b655…2a6f
2 touches
0 conflicts
0x445b51c5…0be4
0x34b655…2a6f
2 touches
0 conflicts
0x705a9a1a…db08
0x34b655…2a6f
2 touches
0 conflicts
0xaf30c163…0fb6
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity