pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,821,283
← previous block
next block →
recent activity
Analyzing
Block #86,821,283
10 transactions · 8 stateful · 2026-07-10 10:33:03 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,821,283
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x938bf18e
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#6
0x3f5c179b
#7
setData
#5
execFwdPositionOps
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x27f19d3a…7851
0x34b655…2a6f
4 touches
1 conflict
0x67e34919…3097
0x34b655…2a6f
4 touches
1 conflict
0x732d520d…c5f9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9cea6ca2…570e
0x34b655…2a6f
4 touches
1 conflict
0xa9504179…c0dc
0x34b655…2a6f
4 touches
1 conflict
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity