pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,555,781
← previous block
next block →
recent activity
Analyzing
Block #71,555,781
9 transactions · 7 stateful · 2026-04-30 17:18:24 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,555,781
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xeffdedb0
#3
updateDataFeedsValuesPartial
#4
0xd53e7c84
#5
modifyLiquidities
#6
0x69f38f58
· blocks 1
#8
setData
#7
0x69f38f58
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
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
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x5f1f6e08…201f
0x188d58…ea8e
2 touches
0 conflicts
0xbd0080d7…9a73
0x188d58…ea8e
2 touches
0 conflicts
0xc6d377b5…e2c0
0x188d58…ea8e
2 touches
0 conflicts
0xc6d377b5…e2c2
0x188d58…ea8e
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