pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,499,282
← previous block
next block →
recent activity
Analyzing
Block #86,499,282
11 transactions · 9 stateful · 2026-07-08 22:38:58 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,499,282
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x00000699
#4
0xed82b078
#5
execFwdPositionOps
#6
0x0c72758b
#7
setData
#8
0x87d0c3…b06e
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0x0cafc99c…d153
0x3bd359…433a
2 touches
0 conflicts
0x409f458b…3688
0x3bd359…433a
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
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
0xd8834cf34a…0d0004
Audit this contract →
← previous block
·
next block →
recent activity