pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,932,390
← previous block
next block →
recent activity
Analyzing
Block #86,932,390
11 transactions · 6 stateful · 2026-07-10 22:55:52 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,932,390
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
cancel
#6
0x3f5c179b
#7
execFwdPositionOps
#8
0x6a5178f0
#9
setData
#10
0x4d0f0d…b1c9
#2
execFwdPositionOps
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
0x0d43cc69…6f83
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f787
0x34b655…2a6f
4 touches
1 conflict
0x33c7a9e0…4810
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbb277c58…e388
0x34b655…2a6f
4 touches
1 conflict
0xd9f1ce2f…bb04
0x34b655…2a6f
4 touches
1 conflict
0xfec3435f…4a72
0x34b655…2a6f
4 touches
1 conflict
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
0x0d43cc69f6…c46f83
Audit this contract →
← previous block
·
next block →
recent activity