pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,643,164
← previous block
next block →
recent activity
Analyzing
Block #71,643,164
14 transactions · 10 stateful · 2026-05-01 03:00:00 UTC
Parallelism
79
/100
Blocked
20
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,643,164
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69f417a8
#2
0x69f417a8
#3
execute
#4
updatePrices
· blocks 2
#7
0x69f417a8
#8
0xeffdedb0
#9
0x9036287a
#10
updateDataFeedsValuesPartial
#11
setData
#12
moveTicks
#13
0x39435dac
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0005
0x094452…0a09
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:
0x7e9d3a8a…4f9fda
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity