pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,528,905
← previous block
next block →
recent activity
Analyzing
Block #95,528,905
10 transactions · 9 stateful · 2026-08-13 03:53:43 UTC
Parallelism
70
/100
Blocked
44
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,528,905
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 3
#3
execOrders
· blocks 1
#4
execFwdPositionOps
#5
executeBatch
#9
updateDataFeedsValuesPartial
#2
0xab083028
#6
0x3f5c179b
· blocks 1
#8
execFwdPositionOps
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
7
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x1d14bff4…4a74
0x40c49f…2af0
4 touches
1 conflict
0xb0586907…49ab
0x34b655…2a6f
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x9045a50c…9bb0
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
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:
0x40c49f17…d22af0
3 conflicts on slot
0x342fbbca09…fcd443
Audit this contract →
← previous block
·
next block →
recent activity