pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,310,164
← previous block
next block →
recent activity
Analyzing
Block #72,310,164
8 transactions · 7 stateful · 2026-05-04 05:08:41 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,310,164
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
0x69f82a51
#3
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
setData
#7
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x7f975651…8c28
0x0555e3…2b9c
2 touches
0 conflicts
0xdb38e047…66c4
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3cce96aa…46c0
0x065c9d…c394
2 touches
0 conflicts
0x62afb756…b854
0x065c9d…c394
2 touches
0 conflicts
0x91fae5c1…23d3
0x065c9d…c394
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:
0x0555e30d…0d2b9c
1 conflict on slot
0x846f21722e…fdfd54
Audit this contract →
← previous block
·
next block →
recent activity