pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,168,766
← previous block
next block →
recent activity
Analyzing
Block #86,168,766
13 transactions · 12 stateful · 2026-07-07 09:51:05 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,168,766
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb264ae19
#2
execute
#3
0xaf5e395a
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updatePriceFeedsIfNecessary
#6
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
#10
setData
#11
execOrders
#12
0xc7e3ec2c
#7
0xed82b078
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x6819a8f2…4392
0x34b655…2a6f
3 touches
1 conflict
0x025caa19…4013
0x065c9d…c394
3 touches
1 conflict
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x197d7800…ca53
0x3bd359…433a
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
0x2f358e74e6…851022
Audit this contract →
← previous block
·
next block →
recent activity