pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,480,787
← previous block
next block →
recent activity
Analyzing
Block #73,480,787
11 transactions · 8 stateful · 2026-05-09 15:03:28 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,480,787
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#4
forward
#5
forward
#6
0xed82b078
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
0x5339c59f
#10
setData
#3
0xd53e7c84
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939088d5…cd10
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x01592765…85b1
0x065c9d…c394
2 touches
0 conflicts
0x0455e253…82ea
0x065c9d…c394
2 touches
0 conflicts
0x1aaf6a1e…09c0
0x065c9d…c394
2 touches
0 conflicts
0xde8d1599…4a73
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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:
0x065c9d28…a9c394
1 conflict on slot
0x939088d5b1…30cd10
Audit this contract →
← previous block
·
next block →
recent activity