pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,972,307
← previous block
next block →
recent activity
Analyzing
Block #72,972,307
11 transactions · 9 stateful · 2026-05-07 06:40:10 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,972,307
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x69fc3442
· blocks 3
#2
updateDataFeedsValuesPartial
#5
setData
#6
forward
#8
0xeffdedb0
#9
0x1dc80c…4cf0
#10
0x785f5745
#3
0x69fc3442
· blocks 2
#4
0x69fc3442
· blocks 1
#7
0x69fc3442
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xc67f584f…a618
0x0c65a0…0852
2 touches
0 conflicts
0x5860c4f3…0c39
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0xbab229…9388
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
6 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity