pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,600,477
← previous block
next block →
recent activity
Analyzing
Block #73,600,477
8 transactions · 5 stateful · 2026-05-10 04:19:09 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,600,477
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x62be7533
#6
setData
#7
0x39435dac
#2
0x0d484c28
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
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x66d594c8…b24d
0x0594c7…a3be
2 touches
0 conflicts
0x761275c9…17a7
0x0594c7…a3be
2 touches
0 conflicts
0x0ebcc580…4e60
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:
0x754704bc…afb603
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity