pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,809,614
← previous block
next block →
recent activity
Analyzing
Block #94,809,614
11 transactions · 9 stateful · 2026-08-10 15:21:21 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,809,614
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
executeBatch
#6
transferWithAuthorization
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21de4cce…a3e9
0x34b655…2a6f
4 touches
1 conflict
0x5a7505f7…a94d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x0a9bbef4…f691
0x34b655…2a6f
2 touches
0 conflicts
0x0f240f9c…61ea
0x34b655…2a6f
2 touches
0 conflicts
0x0f240f9c…61eb
0x34b655…2a6f
2 touches
0 conflicts
0x2c2db8e9…fdc7
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
0x21de4cce39…3ea3e9
Audit this contract →
← previous block
·
next block →
recent activity