pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,047,708
← previous block
next block →
recent activity
Analyzing
Block #86,047,708
13 transactions · 12 stateful · 2026-07-06 20:23:21 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,047,708
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x39435dac
· blocks 1
#6
lockPermanent
#7
redeemDelegations
#8
0x3f5c179b
#9
0x3f5c179b
#10
0x6a4c0f30
#11
setData
#12
0xc7e3ec2c
#5
0x39435dac
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
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0c73c1aa…af05
0x34b655…2a6f
2 touches
0 conflicts
0x35563c03…7689
0x34b655…2a6f
2 touches
0 conflicts
0x814de043…458c
0x34b655…2a6f
2 touches
0 conflicts
0xbe9baf16…df37
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:
Perpl
1 conflict on slot
0x4be9812b87…d748a9
Audit this contract →
← previous block
·
next block →
recent activity