pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,314,724
← previous block
next block →
recent activity
Analyzing
Block #86,314,724
12 transactions · 9 stateful · 2026-07-08 02:05:44 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,314,724
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 1
#3
aggregate3
#5
0x3f5c179b
#6
updateDataFeedsValuesPartial
#7
setData
#8
redeemDelegations
#9
execOrders
#10
execOrders
#11
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x5a79a8ae…c311
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x026864…26e6
2 touches
0 conflicts
0x00000000…0004
0x170763…067c
2 touches
0 conflicts
0x004ab53c…043e
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x311d255f…73b0
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
0xd800e635bc…14b1d7
Audit this contract →
← previous block
·
next block →
recent activity