pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,500,122
← previous block
next block →
recent activity
Analyzing
Block #86,500,122
11 transactions · 8 stateful · 2026-07-08 22:44:34 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,500,122
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
0x0c72758b
· blocks 1
#9
setData
#10
0xa6f524…0273
#8
0x0c72758b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x02c4bb0f…f2c8
0x34b655…2a6f
2 touches
0 conflicts
0x089552b1…a1cd
0x34b655…2a6f
2 touches
0 conflicts
0x0cb4073f…4730
0x34b655…2a6f
2 touches
0 conflicts
0x1ba17872…9dd9
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:
0x2f55a2e1…f48375
1 conflict on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity