pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,575,313
← previous block
next block →
recent activity
Analyzing
Block #85,575,313
9 transactions · 7 stateful · 2026-07-04 15:53:53 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,575,313
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
0xc1fc25…4a20
#7
0xca61ad…4f6d
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7c4db97…948e
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x841318e5…3005
0x34b655…2a6f
4 touches
1 conflict
0x25ecf913…0ad8
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
2 touches
0 conflicts
0xe4af4c87…9964
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
0xa7c4db979d…55948e
Audit this contract →
← previous block
·
next block →
recent activity