pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,157,310
← previous block
next block →
recent activity
Analyzing
Block #86,157,310
12 transactions · 9 stateful · 2026-07-07 08:34:40 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,157,310
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
execOrders
#6
0xed82b078
#7
execFwdPositionOps
#8
0x6a4cba98
#9
setData
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x50fed00e…b35c
0x34b655…2a6f
4 touches
1 conflict
0xc44901fe…0fef
0x34b655…2a6f
4 touches
1 conflict
0xc4cb048e…7562
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xf5e3673b…6254
0x065c9d…c394
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity