pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,263,581
← previous block
next block →
recent activity
Analyzing
Block #73,263,581
10 transactions · 9 stateful · 2026-05-08 14:58:10 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,263,581
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
deposit
#2
0xed82b078
#3
updatePrices
#4
0x39435dac
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x69fdfa7a
#8
0xeffdedb0
#9
setData
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x782b2bf1…87e9
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xe6bc2705…d15b
0x34b655…2a6f
4 touches
1 conflict
0x29654e0d…fb0a
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0c65a0…0852
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
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:
0x34b6552d…112a6f
1 conflict on slot
0x782b2bf15a…e487e9
Audit this contract →
← previous block
·
next block →
recent activity