pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,509,161
← previous block
next block →
recent activity
Analyzing
Block #85,509,161
10 transactions · 7 stateful · 2026-07-04 08:33:22 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,509,161
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0xd60faa87
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
0x5166c9…6d62
#4
swapWithBackendSignature
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
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0xff393f19…4dd2
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0001
0x0d73bf…be07
4 touches
1 conflict
0x3df7769a…5d17
0x3bd359…433a
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x86e5693a…f140
0x065c9d…c394
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:
0x0d73bf86…a6be07
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity