pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,204,361
← previous block
next block →
recent activity
Analyzing
Block #92,204,361
10 transactions · 9 stateful · 2026-08-01 12:38:44 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,204,361
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
execFwdPositionOps
#6
0x6a6de94b
#7
setData
#8
0x59558d29
#9
0xc7e3ec2c
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x3e2663d3…a620
0x34b655…2a6f
4 touches
1 conflict
0x806bf739…e950
0x34b655…2a6f
4 touches
1 conflict
0xa98e6cb0…8051
0x34b655…2a6f
4 touches
1 conflict
0x18d306ad…d8f4
0x34b655…2a6f
2 touches
0 conflicts
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x1de46303…f293
0x34b655…2a6f
2 touches
0 conflicts
0x2f4b1dc8…e9fa
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity