pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,271,717
← previous block
next block →
recent activity
Analyzing
Block #72,271,717
14 transactions · 10 stateful · 2026-05-04 00:51:09 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
#72,271,717
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x98717539
#7
0x3f5c179b
#8
forward
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x36326531
#12
0xad27be…ceec
#13
0x045bc5…7909
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
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
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x01a33778…c2d4
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x3146d553…a2dc
0x34b655…2a6f
2 touches
0 conflicts
0x3f825cc0…11fd
0x34b655…2a6f
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