pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,845,017
← previous block
next block →
recent activity
Analyzing
Block #85,845,017
9 transactions · 8 stateful · 2026-07-05 21:51:06 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,845,017
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#7
0x6a4ad242
#8
setData
#2
0xab083028
· blocks 1
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad63663f…2db4
0x40c49f…2af0
4 touches
1 conflict
0xdaa6e1e3…30e1
0x40c49f…2af0
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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:
0x40c49f17…d22af0
1 conflict on slot
0xad63663f00…472db4
Audit this contract →
← previous block
·
next block →
recent activity