pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,555,531
← previous block
next block →
recent activity
Analyzing
Block #71,555,531
12 transactions · 11 stateful · 2026-04-30 17:16:44 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,555,531
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
revealWithCallback
#3
updatePrices
#4
addLiquidity
#5
0x69f38ef3
· blocks 1
#6
0xeffdedb0
#8
0x0c7abd22
#9
0x3f5c179b
#10
updateDataFeedsValuesPartial
#11
setData
#7
0x69f38ef4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
2 touches
0 conflicts
0x0e8caa47…e172
0x73ada1…8be0
2 touches
0 conflicts
0x3a6ec97d…5976
0x73ada1…8be0
2 touches
0 conflicts
0x6b464b77…020b
0x73ada1…8be0
2 touches
0 conflicts
0x7efa28ac…6a8e
0x73ada1…8be0
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity