pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,041,850
← previous block
next block →
recent activity
Analyzing
Block #73,041,850
20 transactions · 12 stateful · 2026-05-07 14:23:03 UTC
Parallelism
90
/100
Blocked
8
%
Avg conflicts / tx
0.05
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,850
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
approve
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
updatePrices
#11
updatePrices
#12
redeemDelegations
#13
withdraw
#14
modifyLiquidities
#15
updateDataFeedsValuesPartial
#16
0xe9316489
#17
0xeffdedb0
#18
setData
#19
0x39435dac
#4
updatePrices
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
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8fa23737…9b7c
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
0xd574cae5…037ab1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity