pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,643,256
← previous block
next block →
recent activity
Analyzing
Block #71,643,256
15 transactions · 13 stateful · 2026-05-01 03:00:37 UTC
Parallelism
73
/100
Blocked
23
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,643,256
· 15 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x69f417cc
#2
0x69f417cc
#3
0xb264ae19
#4
updatePrices
· blocks 3
#8
handleOps
#9
0xeffdedb0
#10
updateDataFeedsValuesPartial
#11
setData
#12
forward
#13
0x6df9e92b
#14
0x39435dac
#5
updatePrices
· blocks 2
#6
updatePrices
· blocks 1
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x478cdc57…5f1d
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity