pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,576,610
← previous block
next block →
recent activity
Analyzing
Block #93,576,610
10 transactions · 9 stateful · 2026-08-06 07:42:41 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,576,610
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
execFwdPositionOps
#8
0x6a743b69
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ec7fb56…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x1176d678…20ef
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x4bd79f91…4d5b
0x34b655…2a6f
2 touches
0 conflicts
0x6037d3fd…91cf
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
0x982129521c…f19ba6
Audit this contract →
← previous block
·
next block →
recent activity