pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,639
← previous block
next block →
recent activity
Analyzing
Block #70,986,639
11 transactions · 10 stateful · 2026-04-28 02:03:55 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,639
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7ab71841
#2
removeLiquidity
#3
updatePrices
#4
0x0c7abd22
· blocks 2
#7
updateDataFeedsValuesPartial
#8
0x69f01603
· blocks 1
#9
setData
#5
0x6463ffd1
#6
0x0c7abd22
#10
0x69f01603
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x40bba212…07b5
0x065c9d…c394
3 touches
1 conflict
0xf1ba8c5a…a6c5
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x56b9c4fd…f54a
0x481628…4845
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:
0x1b68626d…2de19c
1 conflict on slot
0xcb45d9d62a…b1cb86
Audit this contract →
← previous block
·
next block →
recent activity