pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,194,515
← previous block
next block →
recent activity
Analyzing
Block #88,194,515
13 transactions · 11 stateful · 2026-07-16 19:37:54 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,194,515
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
executeRelayerRefundLeaf
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
forward
#11
setData
#12
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8c255af…052c
0x34b655…2a6f
4 touches
1 conflict
0xdfd4deab…5782
0x34b655…2a6f
4 touches
1 conflict
0x6d597594…10d2
0x34b655…2a6f
4 touches
1 conflict
0xbc4e7b49…3d2d
0x34b655…2a6f
4 touches
1 conflict
0x6d597594…10d1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x97a318be…9349
0x34b655…2a6f
4 touches
1 conflict
0x75672994…7e43
0x34b655…2a6f
3 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
0xb8c255af85…77052c
Audit this contract →
← previous block
·
next block →
recent activity