pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,095,270
← previous block
next block →
recent activity
Analyzing
Block #71,095,270
13 transactions · 12 stateful · 2026-04-28 14:07:18 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,095,270
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0x69f0bf8e
#3
0x98717539
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
#7
0x6df9e92b
#8
updateTemporalNumericValuesV1
#9
setData
#10
updatePrices
· blocks 1
#12
updatePrices
#11
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
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
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
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:
0xc1a5781e…c78e1a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity