pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,853,285
← previous block
next block →
recent activity
Analyzing
Block #101,853,285
9 transactions · 9 stateful · 2026-09-04 08:29:21 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,853,285
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xefa1630b
#3
updateDataFeedsValuesPartial
#4
setData
#6
execOrders
· blocks 2
#5
execFwdPositionOpsV2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
2 touches
0 conflicts
0x24b3f840…ca58
0x34b655…2a6f
2 touches
0 conflicts
0x290abc80…f605
0x34b655…2a6f
2 touches
0 conflicts
0x2d93833d…aa1e
0x34b655…2a6f
2 touches
0 conflicts
0x52cf5603…ca01
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity