pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,892,097
← previous block
next block →
recent activity
Analyzing
Block #70,892,097
13 transactions · 11 stateful · 2026-04-27 15:34:15 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,097
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0x69ef826f
#3
0xb3dd4ec4
#4
updatePrices
· blocks 1
#5
updatePrices
#7
updateDataFeedsValuesPartial
#8
0x6463ffd1
· blocks 1
#9
setData
#10
0xed82b078
#12
updatePrices
#6
updatePrices
#11
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
8
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 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
0x00000000…0004
0x5afd3e…7620
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity