pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,212,575
← previous block
next block →
recent activity
Analyzing
Block #85,212,575
11 transactions · 9 stateful · 2026-07-02 23:38:10 UTC
Parallelism
82
/100
Blocked
33
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,212,575
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#6
forward
#7
setData
#8
execOrders
· blocks 1
#10
execOrders
#4
execFwdPositionOps
#5
0x0c7abd22
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x833ebd97…5abb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5ec7f6b9…f2f0
0x34b655…2a6f
4 touches
1 conflict
0x401339d7…4e2e
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5c0393a4…8b86
0x34b655…2a6f
2 touches
0 conflicts
0x5d4a3441…e31c
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
0x833ebd9703…2b5abb
Audit this contract →
← previous block
·
next block →
recent activity