pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,987,175
← previous block
next block →
recent activity
Analyzing
Block #73,987,175
11 transactions · 10 stateful · 2026-05-11 23:30:57 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,987,175
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a026729
#3
execute
#4
exactOutputSingle
#5
exactOutputSingle
#6
execute
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xbbd593…93e7
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9695f9…0d66
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ba85df7…5be7
0x065c9d…c394
2 touches
0 conflicts
0x5a8ca654…d4cc
0x065c9d…c394
2 touches
0 conflicts
0x8fe4520e…336f
0x065c9d…c394
2 touches
0 conflicts
0x94bff69c…d15c
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:
0xd32edf66…9fff58
1 conflict on slot
0xcd9695f92b…6f0d66
Audit this contract →
← previous block
·
next block →
recent activity