pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,318,862
← previous block
next block →
recent activity
Analyzing
Block #87,318,862
8 transactions · 6 stateful · 2026-07-12 17:59:30 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,318,862
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#6
setData
#7
0xb8024e56
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x38e39eef…50bd
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x027bfcb2…714f
0x34b655…2a6f
2 touches
0 conflicts
0x1cbe4f94…3a9b
0x34b655…2a6f
2 touches
0 conflicts
0x2714ec54…3fb6
0x34b655…2a6f
2 touches
0 conflicts
0x2c3159a6…a84b
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
3 conflicts on slot
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity