pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,911,215
← previous block
next block →
recent activity
Analyzing
Block #70,911,215
10 transactions · 10 stateful · 2026-04-27 17:41:36 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,215
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x69efa048
#3
0x1094dc9f
· blocks 1
#4
0x98717539
#5
forward
#6
updateDataFeedsValuesPartial
#8
modifyLiquidities
#9
setData
#7
updatePosition
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81955a0a…29ee
0x6657d1…8ccc
4 touches
1 conflict
0xeeb8b7fc…24d6
0x6657d1…8ccc
4 touches
1 conflict
0x3923d7de…bb41
0x754704…b603
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x370ef3a4…87c3
0x065c9d…c394
2 touches
0 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
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:
0x6657d192…be8ccc
1 conflict on slot
0x81955a0a11…9a29ee
Audit this contract →
← previous block
·
next block →
recent activity