pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,877,792
← previous block
next block →
recent activity
Analyzing
Block #70,877,792
12 transactions · 9 stateful · 2026-04-27 13:59:04 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,792
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5bf9264c
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#5
forward
· blocks 1
#7
forward
#8
0x69ef6c20
#9
setData
#10
updatePrices
#11
updatePrices
#6
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000d
0x810d5e…d0f1
4 touches
1 conflict
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
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
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:
0x810d5e3d…c6d0f1
1 conflict on slot
0x0000000000…00000d
Audit this contract →
← previous block
·
next block →
recent activity