pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,615,962
← previous block
next block →
recent activity
Analyzing
Block #87,615,962
8 transactions · 7 stateful · 2026-07-14 03:07:14 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,615,962
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
permit2TransferAndMulticall
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
setData
#7
0xf42af5…a401
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x899603fa…742c
0x34b655…2a6f
4 touches
1 conflict
0xe35b84bc…4d5b
0x34b655…2a6f
4 touches
1 conflict
0x11dd03cd…4e54
0x34b655…2a6f
2 touches
0 conflicts
0x1457c480…ae9f
0x34b655…2a6f
2 touches
0 conflicts
0x14c5407b…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x206e0da0…621c
0x34b655…2a6f
2 touches
0 conflicts
0x37ab49be…3b8b
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
0x745952b2a0…a6d90c
Audit this contract →
← previous block
·
next block →
recent activity