pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,978,685
← previous block
next block →
recent activity
Analyzing
Block #94,978,685
10 transactions · 9 stateful · 2026-08-11 05:31:45 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,978,685
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#4
execFwdPositionOps
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0x1a763b77…da66
0x34b655…2a6f
4 touches
1 conflict
0x2794fd34…c82f
0x34b655…2a6f
4 touches
1 conflict
0x70a2eb8e…ba35
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afaa
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
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
0xe58009e820…f6fe3f
Audit this contract →
← previous block
·
next block →
recent activity