pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,167,344
← previous block
next block →
recent activity
Analyzing
Block #85,167,344
11 transactions · 8 stateful · 2026-07-02 18:36:59 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,167,344
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0xed82b078
#6
0x1ba748…9e71
#7
setData
#8
withdraw
#9
execOrders
· blocks 1
#5
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad3280d…16bb
0x34b655…2a6f
4 touches
1 conflict
0xd1fe26e6…8d31
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x181732de…9796
0x34b655…2a6f
2 touches
0 conflicts
0x1c7702cc…ffbe
0x34b655…2a6f
2 touches
0 conflicts
0x258aa9d0…489a
0x34b655…2a6f
2 touches
0 conflicts
0x3ed01bdd…b317
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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
0x5ad3280dca…f116bb
Audit this contract →
← previous block
·
next block →
recent activity