pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,944,769
← previous block
next block →
recent activity
Analyzing
Block #86,944,769
11 transactions · 10 stateful · 2026-07-11 00:18:36 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,944,769
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#5
0x0c9bed1a
#8
0x6a518c54
#9
setData
#10
execOrders
#6
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0x10085190…64b3
0x34b655…2a6f
4 touches
1 conflict
0x8eb888d3…aac7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x74e46435…fdcd
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
0xe1a1a29a1a…3aa399
Audit this contract →
← previous block
·
next block →
recent activity