pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,220,130
← previous block
next block →
recent activity
Analyzing
Block #96,220,130
10 transactions · 9 stateful · 2026-08-15 13:51:59 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,220,130
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x8263f5d9
#2
execOrders
· blocks 1
#3
execOrders
#4
0x3f5c179b
#5
0x3f5c179b
#8
updateDataFeedsValuesPartial
#9
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x61195228…1b60
0x34b655…2a6f
2 touches
0 conflicts
0x6de27d51…4b78
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
0x8d17543904…b6fb79
Audit this contract →
← previous block
·
next block →
recent activity