pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,966,186
← previous block
next block →
recent activity
Analyzing
Block #86,966,186
12 transactions · 11 stateful · 2026-07-11 02:41:41 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,966,186
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
withdraw
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
0x3b073534
#8
0x6a51addd
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa412324b…90aa
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90ab
0x34b655…2a6f
4 touches
1 conflict
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xc99c0798…2960
0x386489…7508
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
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
0xa412324b83…4590aa
Audit this contract →
← previous block
·
next block →
recent activity