pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,312,063
← previous block
next block →
recent activity
Analyzing
Block #87,312,063
6 transactions · 5 stateful · 2026-07-12 17:14:03 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,312,063
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#5
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc5289d2…9d28
0x34b655…2a6f
4 touches
1 conflict
0x03c2acba…6f0e
0x34b655…2a6f
4 touches
1 conflict
0x03c2acba…6f0f
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x85c0f85c…ea7b
0x34b655…2a6f
4 touches
1 conflict
0x8e7e9235…01bb
0x34b655…2a6f
4 touches
1 conflict
0x8e7e9235…01bc
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
0xcc5289d2ca…6c9d28
Audit this contract →
← previous block
·
next block →
recent activity