pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,456,217
← previous block
next block →
recent activity
Analyzing
Block #87,456,217
12 transactions · 10 stateful · 2026-07-13 09:18:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,456,217
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
claimRewards
#6
0x57368ddf
#7
execFwdPositionOps
· blocks 1
#8
batchCancelOrders
#9
updateDataFeedsValuesPartial
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x0f556856…2916
0x34b655…2a6f
2 touches
0 conflicts
0x54255d87…3508
0x34b655…2a6f
2 touches
0 conflicts
0x6aea3f64…bb1f
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
0xdfc21d7c53…51e062
Audit this contract →
← previous block
·
next block →
recent activity