pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,483,775
← previous block
next block →
recent activity
Analyzing
Block #92,483,775
10 transactions · 9 stateful · 2026-08-02 12:03:59 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,483,775
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
batchUpdate
#5
updateDataFeedsValuesPartial
#6
0x6a6f32a7
#7
setData
#8
execOrders
#9
0x59558d29
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x13fa8d63…ba0d
0x34b655…2a6f
2 touches
0 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
2 touches
0 conflicts
0x6246af59…213f
0x34b655…2a6f
2 touches
0 conflicts
0x73f1f4e4…45e5
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity