pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,360,820
← previous block
next block →
recent activity
Analyzing
Block #86,360,820
20 transactions · 16 stateful · 2026-07-08 07:13:33 UTC
Parallelism
90
/100
Blocked
19
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,360,820
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xab083028
#4
0x13572d0b
#5
execFwdPositionOps
· blocks 2
#6
execFwdPositionOps
· blocks 1
#7
updatePosition
#8
0x3f5c179b
#10
closeTrade
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
0x6a4df914
#16
setData
#17
0xcbe3c0…ff98
#19
0xc7e3ec2c
#9
execFwdPositionOps
#11
execFwdPositionOps
#18
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
9
w1
11
w1
18
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x78d7a614…ffff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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
0x997011860a…ad1cbf
Audit this contract →
← previous block
·
next block →
recent activity