pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,939,485
← previous block
next block →
recent activity
Analyzing
Block #85,939,485
11 transactions · 10 stateful · 2026-07-06 08:20:32 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,939,485
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#3
forward
#5
batchUpdate
#6
forward
#7
forward
#8
setData
#10
0xc7e3ec2c
#4
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x52342825…6e5c
0x34b655…2a6f
4 touches
1 conflict
0x8fe2c648…84a8
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xddd7607e…9b4b
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
1 conflict on slot
0x05b1b07aba…747a99
Audit this contract →
← previous block
·
next block →
recent activity