pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,212,015
← previous block
next block →
recent activity
Analyzing
Block #85,212,015
12 transactions · 11 stateful · 2026-07-02 23:34:26 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,212,015
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
0xab083028
#3
updatePrices
· blocks 1
#5
execOrders
· blocks 1
#6
0x5a5d9a99
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#11
0xc7e3ec2c
#4
updatePrices
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2b1c23bc…dabb
0x065c9d…c394
2 touches
0 conflicts
0x57db6ad4…a5ac
0x065c9d…c394
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x921c3e5a…75a2
0x40c49f…2af0
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
0xb44564d6a3…0fbb43
Audit this contract →
← previous block
·
next block →
recent activity