pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,816,805
← previous block
next block →
recent activity
Analyzing
Block #85,816,805
8 transactions · 7 stateful · 2026-07-05 18:43:12 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,816,805
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0x234623f7
· blocks 1
#6
setData
#7
0x7def77…40b8
#5
handleOps
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
0x5e047c95…b44e
0x62ab75…c800
4 touches
1 conflict
0x5e047c95…b454
0x62ab75…c800
4 touches
1 conflict
0x73cb5554…4902
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x62ab75…c800
4 touches
1 conflict
0x5e047c95…b44c
0x62ab75…c800
4 touches
1 conflict
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
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:
0x62ab757c…36c800
1 conflict on slot
0x5e047c956b…17b44e
Audit this contract →
← previous block
·
next block →
recent activity