pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,908,754
← previous block
next block →
recent activity
Analyzing
Block #70,908,754
12 transactions · 12 stateful · 2026-04-27 17:25:12 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.42
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,754
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
0x5bf9264c
#3
multicall
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 2
#6
updatePriceFeedsIfNecessary
#10
setData
#11
0x39435dac
#7
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
5
w0
7
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 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…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
0x065c9d28…a9c394
3 conflicts on slot
0x24968e6db4…f00132
Audit this contract →
← previous block
·
next block →
recent activity