pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,754,659
← previous block
next block →
recent activity
Analyzing
Block #87,754,659
11 transactions · 10 stateful · 2026-07-14 18:34:56 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,754,659
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
0x3f5c179b
#6
execFwdPositionOps
· blocks 1
#8
forward
#9
setData
#10
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x823a3658…acf6
0x34b655…2a6f
4 touches
1 conflict
0xa1185d34…5818
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x28c62bca…b746
0x34b655…2a6f
2 touches
0 conflicts
0x2d8a87f4…9991
0x34b655…2a6f
2 touches
0 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x9ae859db…2d84
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
0x823a3658a2…1bacf6
Audit this contract →
← previous block
·
next block →
recent activity