pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,140,725
← previous block
next block →
recent activity
Analyzing
Block #85,140,725
12 transactions · 12 stateful · 2026-07-02 15:39:45 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,140,725
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updatePosition
#7
forward
#8
0x6a4686b9
#9
setData
#10
execOrders
#11
0x5d2fd812
#2
0x5a5d9a99
· blocks 1
#3
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b353877…605d
0x34b655…2a6f
6 touches
3 conflicts
0xf2112d98…bb04
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x00df1127…6fe4
0x34b655…2a6f
4 touches
1 conflict
0x83d19cb4…b23d
0x34b655…2a6f
4 touches
1 conflict
0xa1144aa9…7f67
0x34b655…2a6f
4 touches
1 conflict
0xc83310b1…c778
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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
3 conflicts on slot
0x5b353877fb…57605d
Audit this contract →
← previous block
·
next block →
recent activity