pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,095,314
← previous block
next block →
recent activity
Analyzing
Block #71,095,314
14 transactions · 9 stateful · 2026-04-28 14:07:36 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,095,314
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x10774900
· blocks 1
#2
0x0f052239
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
updatePrices
#6
addLiquidity
#7
handleOps
#9
createModule
#10
setData
#11
execute
#12
get
#13
0x39435dac
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2859992…a5ca
0x2a68ba…90c5
4 touches
1 conflict
0xb6f851e4…c3c8
0x065c9d…c394
3 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…003d
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xe285999211…69a5ca
Audit this contract →
← previous block
·
next block →
recent activity