pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,644,252
← previous block
next block →
recent activity
Analyzing
Block #87,644,252
11 transactions · 7 stateful · 2026-07-14 06:16:20 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,644,252
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
execFwdPositionOps
· blocks 1
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xd29190…a079
#9
0xf28c1f…72d5
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58503e07…d442
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afaa
0x34b655…2a6f
4 touches
1 conflict
0x8356a041…a532
0x34b655…2a6f
4 touches
1 conflict
0xa7efa115…74f3
0x34b655…2a6f
4 touches
1 conflict
0xab96ac84…a512
0x34b655…2a6f
4 touches
1 conflict
0xd8e46569…4dd1
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
0x58503e0714…dcd442
Audit this contract →
← previous block
·
next block →
recent activity