pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,711
← previous block
next block →
recent activity
Analyzing
Block #70,986,711
13 transactions · 11 stateful · 2026-04-28 02:04:24 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,711
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
forward
#4
0xed82b078
· blocks 1
#6
0xed82b078
#7
0xed82b078
#8
setData
#9
0x34653439
#10
0x39435dac
#11
updatePrices
#12
updatePrices
#5
0xed82b078
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
0x046a928e…0012
0x2a68ba…90c5
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
0x00000000…000b
0x2a347b…e9d3
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x131a2e…0da9
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity