pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,838,314
← previous block
next block →
recent activity
Analyzing
Block #86,838,314
12 transactions · 8 stateful · 2026-07-10 12:26:57 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,838,314
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
forward
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
0x2db6b9…17b8
#9
0xd123c8…3511
#10
exactInputSingle
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdb2111f…1402
0x34b655…2a6f
4 touches
1 conflict
0xbdb2111f…1403
0x34b655…2a6f
4 touches
1 conflict
0xe7516d80…6497
0x34b655…2a6f
4 touches
1 conflict
0xf5042875…9a93
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x94cd6ce2…7b45
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
0xbdb2111f58…061402
Audit this contract →
← previous block
·
next block →
recent activity