pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,126,106
← previous block
next block →
recent activity
Analyzing
Block #86,126,106
12 transactions · 10 stateful · 2026-07-07 05:06:19 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,126,106
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execOrders
· blocks 1
#7
setData
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
execOrders
#11
0xc7e3ec2c
#6
execOrders
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
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x016c34a5…9fb0
0x34b655…2a6f
2 touches
0 conflicts
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x5adda4a7…b840
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
0xec0e022022…becb90
Audit this contract →
← previous block
·
next block →
recent activity