pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,570,926
← previous block
next block →
recent activity
Analyzing
Block #92,570,926
8 transactions · 8 stateful · 2026-08-02 19:22:16 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,570,926
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 2
#4
batchUpdate
#6
forward
#5
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9e15e7b9…9fdf
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x00a4f539…8b4a
0x34b655…2a6f
2 touches
0 conflicts
0x0aa8e3cd…af20
0x34b655…2a6f
2 touches
0 conflicts
0x0abf6897…f2ac
0x34b655…2a6f
2 touches
0 conflicts
0x0b65d0ba…a344
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
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity