pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,594,268
← previous block
next block →
recent activity
Analyzing
Block #85,594,268
11 transactions · 10 stateful · 2026-07-04 18:00:11 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
#85,594,268
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0x3f5c179b
#5
0x3f5c179b
#6
execFwdPositionOps
#7
setData
#8
execOrders
· blocks 1
#10
0xc7e3ec2c
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x7239a7a0…e541
0x34b655…2a6f
4 touches
1 conflict
0xc53843f7…3379
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0x37534430…c68b
0x34b655…2a6f
2 touches
0 conflicts
0x6b2a6570…0e70
0x34b655…2a6f
2 touches
0 conflicts
0x7d8bdc93…c682
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
0x5fe7e1267e…896dd2
Audit this contract →
← previous block
·
next block →
recent activity