pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,361,104
← previous block
next block →
recent activity
Analyzing
Block #85,361,104
10 transactions · 9 stateful · 2026-07-03 16:07:33 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,361,104
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updatePrices
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
setData
#7
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#2
0x6ad2e98b
· blocks 1
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc33bea63…8475
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x56041ca5…90e8
0x851145…3f07
4 touches
1 conflict
0xbf0dcca3…fffa
0x851145…3f07
3 touches
1 conflict
0x342a12bc…c045
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4bfbf321…d4f2
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:
0x851145ea…9f3f07
1 conflict on slot
0xc33bea63a0…348475
Audit this contract →
← previous block
·
next block →
recent activity