pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,239,789
← previous block
next block →
recent activity
Analyzing
Block #86,239,789
22 transactions · 16 stateful · 2026-07-07 17:45:20 UTC
Parallelism
91
/100
Blocked
19
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,239,789
· 22 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
execute
#4
0xe3a3c9cc
#5
updatePrices
#6
execOrders
#7
execOrders
#8
updateDataFeedsValuesPartial
#9
execPerpOps
#10
execPerpOps
#12
forward
#13
updateTemporalNumericValuesV1
#14
execFwdPositionOps
#15
setData
#16
0xecd185…698e
#17
claimRewards
#18
execOrders
· blocks 1
#20
0x5d2fd812
#21
0xc7e3ec2c
#3
exactOutputSingle
#11
0x0c7abd22
#19
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
11
w1
18
w0
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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:
Wrapped MON (WMON)
1 conflict on slot
0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block
·
next block →
recent activity