pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,374,094
← previous block
next block →
recent activity
Analyzing
Block #73,374,094
12 transactions · 9 stateful · 2026-05-09 03:13:30 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,374,094
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6f59ca…ad3d
#3
0x98717539
#4
forward
#5
0xed82b078
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
· blocks 2
#10
0x39435dac
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
2 touches
0 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
2 touches
0 conflicts
0xd49762c9…1359
0x34b655…2a6f
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
0xb91a6f59b9…c8722c
Audit this contract →
← previous block
·
next block →
recent activity