pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,033,938
← previous block
next block →
recent activity
Analyzing
Block #73,033,938
17 transactions · 13 stateful · 2026-05-07 13:30:25 UTC
Parallelism
82
/100
Blocked
15
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,033,938
· 17 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x69fc9469
#3
0x69fc9468
#4
0x69fc9468
#5
updateDataFeedsValuesPartial
#6
updatePrices
· blocks 2
#9
0x5bf9264c
#10
0x5bf9264c
#11
0x98717539
#12
approve
#13
commit
#14
0x69fc9469
#15
0xeffdedb0
#16
setData
#7
updatePrices
· blocks 1
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
0xd574cae5…037ab1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity