pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,381,080
← previous block
next block →
recent activity
Analyzing
Block #70,381,080
12 transactions · 10 stateful · 2026-04-25 06:50:46 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,381,080
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
revealWithCallback
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
#5
0x6463ffd1
· blocks 1
#9
setData
#10
0x39435dac
#11
0x39435dac
#6
swap
· blocks 1
#7
0x39435dac
#8
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x9ad593d5…d051
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0149
0xd45826…f134
2 touches
0 conflicts
0x8ebf69ec…edd3
0xd45826…f134
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
0x8db1e0f2ad…b02fcf
Audit this contract →
← previous block
·
next block →
recent activity