pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,594,658
← previous block
next block →
recent activity
Analyzing
Block #95,594,658
10 transactions · 7 stateful · 2026-08-13 09:24:26 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,594,658
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
setData
#6
0x34653439
#7
0x04f8bc…5896
#8
0x59558d29
#9
execOrders
#4
execFwdPositionOps
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
0x2a4da7e0…f36b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x11a1afac…0273
0x34b655…2a6f
2 touches
0 conflicts
0x19b340df…f4f0
0x34b655…2a6f
2 touches
0 conflicts
0x1cbdfcc7…35cc
0x34b655…2a6f
2 touches
0 conflicts
0x1ec4c748…7c76
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
0x2a4da7e08d…a8f36b
Audit this contract →
← previous block
·
next block →
recent activity