pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,516,483
← previous block
next block →
recent activity
Analyzing
Block #85,516,483
11 transactions · 9 stateful · 2026-07-04 09:22:08 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,516,483
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x4d8dc985
#4
0x0f6795d9
#5
setData
#6
0xb043e8…2f50
#7
redeemDelegations
#8
0x39435dac
· blocks 1
#9
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dbfca40…3899
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3208d244…dab6
0x34b655…2a6f
2 touches
0 conflicts
0x59ff84b2…8274
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0xd29e547b…a1dd
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
0x6dbfca4037…133899
Audit this contract →
← previous block
·
next block →
recent activity