pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,297,126
← previous block
next block →
recent activity
Analyzing
Block #95,297,126
10 transactions · 8 stateful · 2026-08-12 08:23:34 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,297,126
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
#2
executeBatch
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a7c2dfd
#6
setData
#8
execOrders
#7
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc82f66db…833d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x605f05fa…4ebc
0x34b655…2a6f
2 touches
0 conflicts
0x7a4885a1…e7e4
0x34b655…2a6f
2 touches
0 conflicts
0xa5e2fdd2…a81b
0x34b655…2a6f
2 touches
0 conflicts
0xd597209e…9800
0x34b655…2a6f
2 touches
0 conflicts
0xe4af4c87…9964
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity