pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,307,980
← previous block
next block →
recent activity
Analyzing
Block #73,307,980
11 transactions · 9 stateful · 2026-05-08 19:53:40 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,307,980
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
#2
0x1e2a8d…1bcc
#3
updatePrices
#4
0x39435dac
· blocks 1
#5
0x69fe3fbc
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb389d45f…8a4c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x0eddaeb0…6d0b
0x065c9d…c394
2 touches
0 conflicts
0x37b804ac…a766
0x065c9d…c394
2 touches
0 conflicts
0x90bbdaf7…eadb
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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:
Perpl
1 conflict on slot
0xb389d45f2b…a98a4c
Audit this contract →
← previous block
·
next block →
recent activity