pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,288,440
← previous block
next block →
recent activity
Analyzing
Block #72,288,440
10 transactions · 10 stateful · 2026-05-04 02:43:33 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,288,440
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8084c
· blocks 1
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
· blocks 1
#6
updatePosition
#8
setData
#2
0x69f8084c
#7
0xed82b078
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa484c48…e18a
0x065c9d…c394
4 touches
1 conflict
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xd3bc1185…e8ac
0x065c9d…c394
3 touches
1 conflict
0xead03eb9…b38d
0x065c9d…c394
3 touches
1 conflict
0x13131902…0747
0x34b655…2a6f
2 touches
0 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x065c9d28…a9c394
1 conflict on slot
0xfa484c4816…46e18a
Audit this contract →
← previous block
·
next block →
recent activity