pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,248,610
← previous block
next block →
recent activity
Analyzing
Block #85,248,610
10 transactions · 8 stateful · 2026-07-03 03:38:17 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,248,610
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x5a5d9a99
· blocks 1
#6
0x0c7abd22
#7
execFwdPositionOps
· blocks 1
#9
execOrders
#5
0x5a5d9a99
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90e113f8…c8f9
0xc8689a…ee79
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x18e403cf…72be
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x4bfbf321…d4f2
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x9cf2d0bf…8d46
0x34b655…2a6f
4 touches
1 conflict
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: Settlement / Helper
1 conflict on slot
0x90e113f8c1…51c8f9
Audit this contract →
← previous block
·
next block →
recent activity