pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,995,220
← previous block
next block →
recent activity
Analyzing
Block #70,995,220
12 transactions · 8 stateful · 2026-04-28 03:01:06 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,220
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f0236a
#2
0xb264ae19
#3
updatePrices
#4
0x69f0236a
#5
0x69f02369
#6
updateDataFeedsValuesPartial
#7
0x6463ffd1
· blocks 1
#8
setData
#9
0x5de3085d
#10
deposit
#11
0x40e79b1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37cd5a8f…f184
0x065c9d…c394
3 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
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…0002
0xb857c1…9be1
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
1 conflict on slot
0x37cd5a8f54…a8f184
Audit this contract →
← previous block
·
next block →
recent activity