pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,633
← previous block
next block →
recent activity
Analyzing
Block #70,986,633
7 transactions · 6 stateful · 2026-04-28 02:03:53 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,633
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
#2
exactInputSingle
#3
0x6463ffd1
· blocks 1
#4
updateDataFeedsValuesPartial
#6
setData
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8417700…f6fd
0x065c9d…c394
4 touches
1 conflict
0x82754758…a06b
0x065c9d…c394
4 touches
1 conflict
0x9c2147d2…4674
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0945800c…544d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xb9c94a07…90bf
0x065c9d…c394
2 touches
1 conflict
0x558c1c7f…d604
0x065c9d…c394
2 touches
1 conflict
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
0xe84177008e…3ff6fd
Audit this contract →
← previous block
·
next block →
recent activity