pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,808,191
← previous block
next block →
recent activity
Analyzing
Block #86,808,191
9 transactions · 8 stateful · 2026-07-10 09:05:24 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,808,191
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a50b64b
#8
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x683dbabb…acd8
0x34b655…2a6f
4 touches
1 conflict
0x98460be4…2ef8
0x34b655…2a6f
4 touches
1 conflict
0xd2771e4d…705d
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x1586ff62…0ebe
0x34b655…2a6f
2 touches
0 conflicts
0x1586ff62…0ebf
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
0x683dbabb7f…33acd8
Audit this contract →
← previous block
·
next block →
recent activity