pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,596,807
← previous block
next block →
recent activity
Analyzing
Block #87,596,807
13 transactions · 9 stateful · 2026-07-14 00:59:09 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,596,807
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
execFwdPositionOps
#8
0x6a558a55
#9
setData
#10
0x2b1023…5bf5
#11
0xcaaa00…0c5d
#12
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa190f35e…7057
0x34b655…2a6f
4 touches
1 conflict
0x369883e3…a449
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0181bb37…6628
0x34b655…2a6f
2 touches
0 conflicts
0x0181bb37…6629
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
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
0xa190f35ec5…567057
Audit this contract →
← previous block
·
next block →
recent activity