pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,366,025
← previous block
next block →
recent activity
Analyzing
Block #86,366,025
11 transactions · 8 stateful · 2026-07-08 07:48:11 UTC
Parallelism
73
/100
Blocked
38
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,366,025
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
· blocks 1
#1
execFwdPositionOps
· blocks 2
#2
updateDataFeedsValuesPartial
#3
0xd708c5d8
#4
0x6a4e0133
#5
setData
#6
0xd14df2…b3a1
#7
exactInputSingle
#8
compound
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
1
w0
8
w1
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
4 touches
1 conflict
0x8e507257…71c1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0xedf4636f…b2a2
0x34b655…2a6f
4 touches
1 conflict
0x6cdad76f…2bed
0x34b655…2a6f
4 touches
1 conflict
0x2f0ec586…3c98
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7214
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity