pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,046,483
← previous block
next block →
recent activity
Analyzing
Block #73,046,483
13 transactions · 10 stateful · 2026-05-07 14:53:56 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,046,483
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x8002ff…8fce
#3
0xb264ae19
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#8
updateDataFeedsValuesPartial
#9
forward
#10
0x6df9e92b
#11
0xeffdedb0
#12
setData
#7
0x55e58ed0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x09f880…ede0
4 touches
1 conflict
0xcc77b33c…6e87
0x3bd359…433a
4 touches
1 conflict
0xbb6daa0c…9f5f
0x522705…fcd0
4 touches
1 conflict
0xdc7a27e1…d536
0x754704…b603
4 touches
1 conflict
0xe436ef16…99df
0x754704…b603
4 touches
1 conflict
0xfe49740d…4e57
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0x09f880…ede0
4 touches
1 conflict
0x00000000…0003
0xab3526…fa38
4 touches
1 conflict
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:
0x09f880cc…e1ede0
1 conflict on slot
0x0000000000…00000a
Audit this contract →
← previous block
·
next block →
recent activity