pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,963,906
← previous block
next block →
recent activity
Analyzing
Block #73,963,906
10 transactions · 8 stateful · 2026-05-11 20:54:59 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,963,906
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
execute
#3
approve
· blocks 1
#5
0xccf50a51
#6
updateDataFeedsValuesPartial
#7
forward
#8
setData
#9
0x39435dac
#4
0x9025acd4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbecfb96…3e12
0xd10cf1…7777
2 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
0x03db766f…f285
0x065c9d…c394
2 touches
0 conflicts
0x3e41a53e…bd0f
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x923c3097…ec5a
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:
0xd10cf120…657777
1 conflict on slot
0xcbecfb968a…a23e12
Audit this contract →
← previous block
·
next block →
recent activity