pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,791,914
← previous block
next block →
recent activity
Analyzing
Block #85,791,914
10 transactions · 8 stateful · 2026-07-05 15:57:24 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,791,914
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
0x6a4a7f5b
#6
setData
#7
0x3b9070…4d61
#8
0x2c785f…edcf
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d0f220…01f4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x14a71e9b…8870
0x34b655…2a6f
2 touches
0 conflicts
0x205bd68b…2a21
0x34b655…2a6f
2 touches
0 conflicts
0x275f56fe…dcfb
0x34b655…2a6f
2 touches
0 conflicts
0x57b73d86…2fcb
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
0x34b655…2a6f
2 touches
0 conflicts
0x6e478775…7197
0x34b655…2a6f
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
0x38d0f220b3…5301f4
Audit this contract →
← previous block
·
next block →
recent activity