pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,343,645
← previous block
next block →
recent activity
Analyzing
Block #73,343,645
10 transactions · 8 stateful · 2026-05-08 23:50:57 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,343,645
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xeffdedb0
#9
0x39435dac
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa1f0ac2…a4c6
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x4829d008…e5fa
0x34b655…2a6f
2 touches
0 conflicts
0x64461c10…e86d
0x34b655…2a6f
2 touches
0 conflicts
0xa15427f6…d932
0x34b655…2a6f
2 touches
0 conflicts
0xb91a6f59…722c
0x34b655…2a6f
2 touches
0 conflicts
0xc855fab5…ae2f
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:
0xd32edf66…9fff58
1 conflict on slot
0xaa1f0ac2e7…99a4c6
Audit this contract →
← previous block
·
next block →
recent activity