pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,630,936
← previous block
next block →
recent activity
Analyzing
Block #81,630,936
11 transactions · 10 stateful · 2026-06-16 09:18:34 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,630,936
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updatePrices
· blocks 1
#4
updatePrices
#6
addLiquidityNATIVE
#7
0x98717539
#8
redeemDelegations
· blocks 1
#9
setData
#5
updatePrices
#10
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xb90b53…8e5c
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0xb90b530c…cb8e5c
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity