pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,301,486
← previous block
next block →
recent activity
Analyzing
Block #72,301,486
10 transactions · 7 stateful · 2026-05-04 04:10:52 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,301,486
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f81cc4
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x3f5c179b
#7
forward
#8
0x69f81cc4
#9
execute
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x389958d5…9ab8
0x065c9d…c394
2 touches
0 conflicts
0x76d27e96…c548
0x065c9d…c394
2 touches
0 conflicts
0x90c1fed7…8337
0x065c9d…c394
2 touches
0 conflicts
0x96872bf7…5ed4
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:
0x34b6552d…112a6f
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity