pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,335,903
← previous block
next block →
recent activity
Analyzing
Block #86,335,903
14 transactions · 10 stateful · 2026-07-08 04:27:12 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,335,903
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
updatePrices
#4
0x39435dac
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x39435dac
#9
setData
#10
0x39435dac
· blocks 1
#12
0x5d2fd812
#13
0xc7e3ec2c
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x851ff3c1…1b15
0x34b655…2a6f
4 touches
1 conflict
0xb4aa41e0…f123
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
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
0x851ff3c1a9…d81b15
Audit this contract →
← previous block
·
next block →
recent activity