pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,931,109
← previous block
next block →
recent activity
Analyzing
Block #85,931,109
10 transactions · 8 stateful · 2026-07-06 07:24:39 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,931,109
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#3
modifyLiquidities
#4
0xb0435a94
#6
0x0f6795d9
#7
setData
#8
0x3a8afe…d517
#9
0x39435dac
#5
0x0f6795d9
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
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xf0e0dffc…9b54
0x34b655…2a6f
4 touches
1 conflict
0xf786d280…163b
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xa8261c44…e3b4
0x188d58…ea8e
2 touches
0 conflicts
0xa8261c44…e3b5
0x188d58…ea8e
2 touches
0 conflicts
0x31616f97…1acc
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xafd867b7ed…d92b2d
Audit this contract →
← previous block
·
next block →
recent activity