pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,722,973
← previous block
next block →
recent activity
Analyzing
Block #87,722,973
13 transactions · 13 stateful · 2026-07-14 15:02:58 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,722,973
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
updatePrices
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a565019
#10
setData
#11
execOrders
#12
0xc7e3ec2c
#4
updatePrices
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
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0304b7a7…9442
0x34b655…2a6f
2 touches
0 conflicts
0x0d90e16c…ffcd
0x34b655…2a6f
2 touches
0 conflicts
0x154f65cf…14d6
0x34b655…2a6f
2 touches
0 conflicts
0x1b6675dd…5b4e
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:
0xc1ff9fef…f4b0fc
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity