pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,786,293
← previous block
next block →
recent activity
Analyzing
Block #86,786,293
11 transactions · 10 stateful · 2026-07-10 06:39:08 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,786,293
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x6a509403
#4
execFwdPositionOps
· blocks 1
#6
0xed82b078
#7
commit
#8
execFwdPositionOps
#9
setData
#10
0xb0e56f…5696
#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
0xc6a72539…9ecb
0x34b655…2a6f
4 touches
1 conflict
0xa444004d…1c9f
0x34b655…2a6f
4 touches
1 conflict
0xa444004d…1ca0
0x34b655…2a6f
4 touches
1 conflict
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x12bc23cf…d56d
0x34b655…2a6f
2 touches
0 conflicts
0x4c43bbae…1403
0x34b655…2a6f
2 touches
0 conflicts
0xefcaccf2…c083
0x34b655…2a6f
2 touches
0 conflicts
0xf7ef0c17…df1d
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
0xc6a72539b8…a49ecb
Audit this contract →
← previous block
·
next block →
recent activity