pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,263,335
← previous block
next block →
recent activity
Analyzing
Block #73,263,335
10 transactions · 10 stateful · 2026-05-08 14:56:33 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,263,335
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
requestRedeem
#2
updatePrices
#3
0x98717539
· blocks 1
#4
redeemDelegations
#5
updateDataFeedsValuesPartial
#6
forward
#7
0xeffdedb0
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb378025c…30cf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0009
0x0c65a0…0852
2 touches
0 conflicts
0x3071cf64…02ac
0x0c65a0…0852
2 touches
0 conflicts
0xa5e083bb…11e7
0x0c65a0…0852
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x313f2565…5b00
0x34b655…2a6f
2 touches
0 conflicts
0x37179c06…3c8c
0x34b655…2a6f
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
0xb378025c92…8630cf
Audit this contract →
← previous block
·
next block →
recent activity