pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,999,349
← previous block
next block →
recent activity
Analyzing
Block #70,999,349
11 transactions · 9 stateful · 2026-04-28 03:28:31 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,999,349
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x69f029d6
#3
0x5bf9264c
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
#7
0x69f029d6
#8
setData
#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
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x34bb851e…8cac
0x065c9d…c394
2 touches
0 conflicts
0x6a1090d1…1894
0x065c9d…c394
2 touches
0 conflicts
0xd53e731b…5657
0x065c9d…c394
2 touches
0 conflicts
0xe7e7fd3f…455c
0x065c9d…c394
2 touches
0 conflicts
0x13b1d959…1c28
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x408e66bba7…d43d6b
Audit this contract →
← previous block
·
next block →
recent activity