pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,862,522
← previous block
next block →
recent activity
Analyzing
Block #70,862,522
11 transactions · 10 stateful · 2026-04-27 12:17:21 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,862,522
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x1a945f9c
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
#7
setData
#8
multicall
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa92c8763…6d7f
0x34b655…2a6f
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…0002
0xb857c1…9be1
2 touches
0 conflicts
0x0869a723…09b8
0x1efe02…37d6
2 touches
0 conflicts
0xe666cb6c…81bf
0x1efe02…37d6
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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
0xa92c87634b…146d7f
Audit this contract →
← previous block
·
next block →
recent activity