pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,897,128
← previous block
next block →
recent activity
Analyzing
Block #85,897,128
10 transactions · 8 stateful · 2026-07-06 03:38:14 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,897,128
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe2dc7dc3
#2
aggregate3
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0xed82b078
#8
setData
#9
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf29257f7…f4d9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd3414a4a…b17f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x0dad2249…8402
0x1efe02…37d6
2 touches
0 conflicts
0x60a0266a…2ef3
0x1efe02…37d6
2 touches
0 conflicts
0x67dec63f…aee8
0x1efe02…37d6
2 touches
0 conflicts
0xdca56c63…0fb9
0x1efe02…37d6
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
0xf29257f72b…e1f4d9
Audit this contract →
← previous block
·
next block →
recent activity