pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,733,003
← previous block
next block →
recent activity
Analyzing
Block #86,733,003
11 transactions · 8 stateful · 2026-07-10 00:43:11 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,733,003
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
0x6a504097
#8
setData
#9
0x4b3a0f…bead
#10
execOrders
#5
execFwdPositionOps
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
0xf45f2405…c8f9
0x34b655…2a6f
4 touches
1 conflict
0x676d5418…85ea
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x44382c57…ae34
0x34b655…2a6f
2 touches
0 conflicts
0x7b6c252d…a696
0x34b655…2a6f
2 touches
0 conflicts
0xb104db11…2208
0x34b655…2a6f
2 touches
0 conflicts
0xb13b96bd…a3cb
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
0xf45f24056b…37c8f9
Audit this contract →
← previous block
·
next block →
recent activity