pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,787,637
← previous block
next block →
recent activity
Analyzing
Block #86,787,637
12 transactions · 8 stateful · 2026-07-10 06:48:07 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,787,637
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
metacall
#3
execFwdPositionOps
· blocks 1
#5
execOrders
#6
execFwdPositionOps
#7
setData
#8
0x248116…4ee8
#9
0x03107e…8558
#10
0x00791f…6c28
#11
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x119694b6…b8dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0x2da28f…75e8
2 touches
0 conflicts
0xf334fe53…11d8
0x2da28f…75e8
2 touches
0 conflicts
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity