pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,515,506
← previous block
next block →
recent activity
Analyzing
Block #85,515,506
7 transactions · 6 stateful · 2026-07-04 09:15:37 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,515,506
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
redeemDelegations
#4
updateDataFeedsValuesPartial
#5
0x6a48cfb1
#6
setData
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x042f82fe…3548
0x34b655…2a6f
2 touches
0 conflicts
0x1f0acb46…bb29
0x34b655…2a6f
2 touches
0 conflicts
0x383481eb…9df3
0x34b655…2a6f
2 touches
0 conflicts
0x43ffd8bd…0d0c
0x34b655…2a6f
2 touches
0 conflicts
0x463e211b…73c9
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
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
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity